BUG: soft lockup in hsr_announce (2)

4 views
Skip to first unread message

syzbot

unread,
Jul 20, 2021, 4:52:20 PM7/20/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4938296e03bd Linux 4.19.198
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16e09754300000
kernel config: https://syzkaller.appspot.com/x/.config?x=9013c716691ad1fe
dashboard link: https://syzkaller.appspot.com/bug?extid=039817a54f5a177dddb5
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+039817...@syzkaller.appspotmail.com

watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [syz-executor.2:10505]
Modules linked in:
irq event stamp: 4825447
hardirqs last enabled at (4825446): [<ffffffff81003ce4>] trace_hardirqs_on_thunk+0x1a/0x1c
hardirqs last disabled at (4825447): [<ffffffff81003d00>] trace_hardirqs_off_thunk+0x1a/0x1c
softirqs last enabled at (4782964): [<ffffffff88400678>] __do_softirq+0x678/0x980 kernel/softirq.c:318
softirqs last disabled at (4782967): [<ffffffff81392705>] invoke_softirq kernel/softirq.c:372 [inline]
softirqs last disabled at (4782967): [<ffffffff81392705>] irq_exit+0x215/0x260 kernel/softirq.c:412
CPU: 1 PID: 10505 Comm: syz-executor.2 Not tainted 4.19.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:read_pnet include/net/net_namespace.h:307 [inline]
RIP: 0010:dev_net include/linux/netdevice.h:2158 [inline]
RIP: 0010:packet_rcv+0xb8/0x1480 net/packet/af_packet.c:2054
Code: 00 00 fc ff df 48 8b 5b 28 48 8d 7b 30 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 7c 11 00 00 49 8d bc 24 80 05 00 00 4c 8b 7b 30 <48> b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f
RSP: 0018:ffff8880ba1078d8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: dffffc0000000000 RBX: ffff888047b703c0 RCX: ffffffff8720530f
RDX: 1ffff11008f6e07e RSI: ffffffff8720531a RDI: ffff88804ca6ec80
RBP: ffff888042e13440 R08: 0000000000000000 R09: 0000000000000005
R10: 0000000000000001 R11: 000000008a64fb14 R12: ffff88804ca6e700
R13: 0000000000000004 R14: ffff888042e134d0 R15: ffff88804fe0c0c0
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc3cc256fc0 CR3: 000000020821c000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
deliver_skb net/core/dev.c:1956 [inline]
dev_queue_xmit_nit+0x24d/0xa20 net/core/dev.c:2012
xmit_one net/core/dev.c:3252 [inline]
dev_hard_start_xmit+0xaa/0x920 net/core/dev.c:3272
__dev_queue_xmit+0x269d/0x2e00 net/core/dev.c:3838
hsr_xmit net/hsr/hsr_forward.c:237 [inline]
hsr_forward_do net/hsr/hsr_forward.c:295 [inline]
hsr_forward_skb+0xd2d/0x1c30 net/hsr/hsr_forward.c:373
send_hsr_supervision_frame+0x917/0xf70 net/hsr/hsr_device.c:321
hsr_announce+0x125/0x3a0 net/hsr/hsr_device.c:350
call_timer_fn+0x177/0x700 kernel/time/timer.c:1338
expire_timers+0x243/0x4e0 kernel/time/timer.c:1375
__run_timers kernel/time/timer.c:1696 [inline]
run_timer_softirq+0x21c/0x670 kernel/time/timer.c:1709
__do_softirq+0x265/0x980 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:372 [inline]
irq_exit+0x215/0x260 kernel/softirq.c:412
exiting_irq arch/x86/include/asm/apic.h:536 [inline]
smp_apic_timer_interrupt+0x136/0x550 arch/x86/kernel/apic/apic.c:1098
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:894
</IRQ>
RIP: 0010:mm_update_next_owner+0x3ae/0x650 kernel/exit.c:452
Code: 20 00 44 89 ee e8 c2 c6 29 00 45 85 ed 0f 85 6f ff ff ff e8 44 c5 29 00 48 8d bd 30 03 00 00 48 89 f8 48 c1 e8 03 80 3c 18 00 <0f> 85 52 02 00 00 48 8b ad 30 03 00 00 4c 8d 6d 10 4c 89 e8 48 c1
RSP: 0018:ffff8881e0d47a98 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 1ffff11007fb6538 RBX: dffffc0000000000 RCX: ffffffff8138bcce
RDX: 0000000000000000 RSI: ffffffff8138bcdc RDI: ffff88803fdb29c0
RBP: ffff88803fdb2690 R08: ffff8880996da6e0 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888206b5c440
R13: 0000000000000000 R14: ffff888207b045c0 R15: ffff88804a89aa00
exit_mm kernel/exit.c:548 [inline]
do_exit+0xae4/0x2be0 kernel/exit.c:857
do_group_exit+0x125/0x310 kernel/exit.c:967
get_signal+0x3f2/0x1f70 kernel/signal.c:2589
do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:799
exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4665e9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc3cc257218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 000000000056bf88 RCX: 00000000004665e9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000000000056bf88
RBP: 000000000056bf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf8c
R13: 00007fffebbbe3ff R14: 00007fc3cc257300 R15: 0000000000022000
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 10510 Comm: syz-executor.2 Not tainted 4.19.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__read_once_size include/linux/compiler.h:261 [inline]
RIP: 0010:queued_write_lock_slowpath+0x11f/0x290 kernel/locking/qrwlock.c:88
Code: 03 41 83 e7 07 4c 8d 2c 02 41 83 c7 03 41 0f b6 45 00 41 38 c7 7c 08 84 c0 0f 85 34 01 00 00 8b 03 3d 00 01 00 00 74 1a f3 90 <41> 0f b6 45 00 41 38 c7 7c eb 84 c0 74 e7 48 89 df e8 7b 53 4c 00
RSP: 0018:ffff8881f5fc7a40 EFLAGS: 00000006
RAX: 0000000000000300 RBX: ffffffff89e09080 RCX: ffffffff814bfcb6
RDX: 1ffffffff13c1210 RSI: 0000000000000004 RDI: ffffffff89e09080
RBP: 1ffff1103ebf8f49 R08: 0000000000000001 R09: fffffbfff13c1210
R10: ffffffff89e09083 R11: 0000000000000000 R12: ffffffff89e09084
R13: fffffbfff13c1210 R14: ffff8881f5fc7a68 R15: 0000000000000003
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000200 CR3: 000000020821c000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
queued_write_lock include/asm-generic/qrwlock.h:103 [inline]
do_raw_write_lock+0xcf/0x1e0 kernel/locking/spinlock_debug.c:203
exit_notify kernel/exit.c:715 [inline]
do_exit+0xc41/0x2be0 kernel/exit.c:890
do_group_exit+0x125/0x310 kernel/exit.c:967
get_signal+0x3f2/0x1f70 kernel/signal.c:2589
do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:799
exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath+0x3f0/0x4a0 arch/x86/entry/common.c:271
ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:407
RIP: 0033:0x467a11
Code: 48 85 ff 74 3d 48 85 f6 74 38 48 83 ee 10 48 89 4e 08 48 89 3e 48 89 d7 4c 89 c2 4d 89 c8 4c 8b 54 24 08 b8 38 00 00 00 0f 05 <48> 85 c0 7c 13 74 01 c3 31 ed 58 5f ff d0 48 89 c7 b8 3c 00 00 00
RSP: 002b:00007fc3cc2362f0 EFLAGS: 00000206 ORIG_RAX: 0000000000000038
RAX: 0000000000000000 RBX: 00007fc3cc236700 RCX: 0000000000467a11
RDX: 00007fc3cc2369d0 RSI: 00007fc3cc2362f0 RDI: 00000000003d0f00
RBP: 00007fffebbbe580 R08: 00007fc3cc236700 R09: 00007fc3cc236700
R10: 00007fc3cc2369d0 R11: 0000000000000206 R12: 00007fffebbbe3fe
R13: 00007fffebbbe3ff R14: 00007fc3cc236300 R15: 0000000000022000


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Feb 15, 2023, 6:56:33 AM2/15/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages