BUG: soft lockup in hsr_announce

7 views
Skip to first unread message

syzbot

unread,
Nov 29, 2019, 8:25:09 PM11/29/19
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 81b6b964 Merge branch 'master' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16c432dae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=333b76551307b2a0
dashboard link: https://syzkaller.appspot.com/bug?extid=7ccc911be1cc4bcf23c5
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [arvid....@alten.se da...@davemloft.net
linux-...@vger.kernel.org net...@vger.kernel.org]

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

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

watchdog: BUG: soft lockup - CPU#2 stuck for 123s! [syz-executor.0:8070]
Modules linked in:
irq event stamp: 4603557
hardirqs last enabled at (4603556): [<ffffffff81006743>]
trace_hardirqs_on_thunk+0x1a/0x1c arch/x86/entry/thunk_64.S:41
hardirqs last disabled at (4603557): [<ffffffff8100675f>]
trace_hardirqs_off_thunk+0x1a/0x1c arch/x86/entry/thunk_64.S:42
softirqs last enabled at (399470): [<ffffffff87e006cd>]
__do_softirq+0x6cd/0x98c kernel/softirq.c:319
softirqs last disabled at (474949): [<ffffffff81474a2b>] invoke_softirq
kernel/softirq.c:373 [inline]
softirqs last disabled at (474949): [<ffffffff81474a2b>]
irq_exit+0x19b/0x1e0 kernel/softirq.c:413
CPU: 2 PID: 8070 Comm: syz-executor.0 Not tainted 5.4.0-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014
RIP: 0010:__skb_put_padto include/linux/skbuff.h:3193 [inline]
RIP: 0010:skb_put_padto include/linux/skbuff.h:3212 [inline]
RIP: 0010:send_hsr_supervision_frame+0xc28/0xf20 net/hsr/hsr_device.c:303
Code: e8 cc e2 96 f9 0f 0b e9 e6 fc ff ff e8 41 2e c6 f9 bb 42 00 00 00 ba
01 00 00 00 4c 89 e7 44 29 f3 89 de e8 ca f9 56 fe 31 ff <41> 89 c6 89 c6
e8 9e 2f c6 f9 45 85 f6 0f 85 84 fc ff ff e8 10 2e
RSP: 0018:ffff88802d409c58 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000000 RBX: 0000000000000028 RCX: 0000000000000000
RDX: 0000000000000100 RSI: ffffffff8605ac22 RDI: 0000000000000000
RBP: ffff88802d409cd0 R08: 1ffff11003866e0b R09: ffff88801c33705c
R10: ffffed1003866e10 R11: ffff88801c337083 R12: ffff88802653dd00
R13: ffff88800e51ce80 R14: 000000000000001a R15: 0000000000000282
FS: 00007f566f90c700(0000) GS:ffff88802d400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffff600400 CR3: 000000006ba25000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
hsr_announce+0x12f/0x3b0 net/hsr/hsr_device.c:334
call_timer_fn+0x1ac/0x780 kernel/time/timer.c:1404
expire_timers kernel/time/timer.c:1449 [inline]
__run_timers kernel/time/timer.c:1773 [inline]
__run_timers kernel/time/timer.c:1740 [inline]
run_timer_softirq+0x6c3/0x1790 kernel/time/timer.c:1786
__do_softirq+0x262/0x98c kernel/softirq.c:292
invoke_softirq kernel/softirq.c:373 [inline]
irq_exit+0x19b/0x1e0 kernel/softirq.c:413
exiting_irq arch/x86/include/asm/apic.h:536 [inline]
smp_apic_timer_interrupt+0x1a3/0x610 arch/x86/kernel/apic/apic.c:1137
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:829
</IRQ>
RIP: 0010:__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:169
[inline]
RIP: 0010:_raw_spin_unlock_irq+0x4f/0x80 kernel/locking/spinlock.c:199
Code: c0 68 34 53 89 48 ba 00 00 00 00 00 fc ff df 48 c1 e8 03 80 3c 10 00
75 33 48 83 3d 12 2a 99 01 00 74 20 fb 66 0f 1f 44 00 00 <bf> 01 00 00 00
e8 e7 6b 96 f9 65 8b 05 18 14 48 78 85 c0 74 06 41
RSP: 0018:ffff88807152f8d8 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff13
RAX: 1ffffffff12a668d RBX: ffff888071524080 RCX: 0000000000000006
RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff888071524914
RBP: ffff88807152f8e0 R08: 1ffffffff15d29b8 R09: fffffbfff15d29b9
R10: fffffbfff15d29b8 R11: ffffffff8ae94dc7 R12: ffff88802d437380
R13: ffff88802c4bc3c0 R14: ffff88802130c580 R15: 0000000000000000
finish_lock_switch kernel/sched/core.c:3124 [inline]
finish_task_switch+0x147/0x750 kernel/sched/core.c:3224
context_switch kernel/sched/core.c:3388 [inline]
__schedule+0x8e9/0x1f30 kernel/sched/core.c:4081
preempt_schedule_common+0x4f/0xe0 kernel/sched/core.c:4236
preempt_schedule+0x4b/0x60 kernel/sched/core.c:4261
___preempt_schedule+0x16/0x18 arch/x86/entry/thunk_64.S:50
smp_call_function_single+0x410/0x480 kernel/smp.c:313
task_function_call+0xe9/0x180 kernel/events/core.c:114
perf_install_in_context+0x308/0x5a0 kernel/events/core.c:2746
__do_sys_perf_event_open+0x1cbc/0x2c70 kernel/events/core.c:11543
__se_sys_perf_event_open kernel/events/core.c:11151 [inline]
__x64_sys_perf_event_open+0xbe/0x150 kernel/events/core.c:11151
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a759
Code: bd b1 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 0f 83 8b b1 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f566f90bc88 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 000000000071bf00 RCX: 000000000045a759
RDX: ffffffffffffffff RSI: 0000000000000000 RDI: 000000002001d000
RBP: 0000000000000005 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 00007f566f90c6d4
R13: 00000000004aec2b R14: 00000000006f1ca8 R15: 00000000ffffffff
Sending NMI from CPU 2 to CPUs 0-1,3:
NMI backtrace for cpu 3 skipped: idling at native_safe_halt+0xe/0x10
arch/x86/include/asm/irqflags.h:60
NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0x10
arch/x86/include/asm/irqflags.h:60
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0x10
arch/x86/include/asm/irqflags.h:60


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Dmitry Vyukov

unread,
Nov 30, 2019, 11:49:55 AM11/30/19
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
false hang on the new qemu instance
#syz invalid
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/0000000000008b08d10598863778%40google.com.
Reply all
Reply to author
Forward
0 new messages