BUG: soft lockup in smp_call_function_many

83 views
Skip to first unread message

syzbot

unread,
Apr 14, 2018, 1:02:04 PM4/14/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot hit the following crash on upstream commit
1bad9ce155a7c010a9a5f3261ad12a6a8eccfb2c (Fri Apr 13 19:27:11 2018 +0000)
Merge tag 'sh-for-4.17' of git://git.libc.org/linux-sh
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=2c624e08665b7becc11b

Unfortunately, I don't have any reproducer for this crash yet.
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=5090094985773056
Kernel config:
https://syzkaller.appspot.com/x/.config?id=-5947642240294114534
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [aaro...@intel.com adob...@gmail.com ak...@linux-foundation.org
fred...@kernel.org linux-...@vger.kernel.org mi...@kernel.org
pet...@infradead.org tg...@linutronix.de ying....@intel.com]

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+2c624e...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.

watchdog: BUG: soft lockup - CPU#1 stuck for 134s! [syz-executor5:9055]
Modules linked in:
irq event stamp: 320166
hardirqs last enabled at (320165): [<ffffffff876009d5>]
restore_regs_and_return_to_kernel+0x0/0x2b
hardirqs last disabled at (320166): [<ffffffff87600901>]
interrupt_entry+0xb1/0xf0 arch/x86/entry/entry_64.S:624
softirqs last enabled at (122752): [<ffffffff87800778>]
__do_softirq+0x778/0xaf5 kernel/softirq.c:311
softirqs last disabled at (122677): [<ffffffff8146fce1>] invoke_softirq
kernel/softirq.c:365 [inline]
softirqs last disabled at (122677): [<ffffffff8146fce1>]
irq_exit+0x1d1/0x200 kernel/softirq.c:405
CPU: 1 PID: 9055 Comm: syz-executor5 Not tainted 4.16.0+ #1
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:rep_nop arch/x86/include/asm/processor.h:667 [inline]
RIP: 0010:cpu_relax arch/x86/include/asm/processor.h:672 [inline]
RIP: 0010:csd_lock_wait kernel/smp.c:108 [inline]
RIP: 0010:smp_call_function_single+0x3e0/0x5b0 kernel/smp.c:302
RSP: 0018:ffff8801856464e0 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: ffff8801ac9ce080 RBX: ffff8801856465d8 RCX: ffffffff816b56a2
RDX: 0000000000000000 RSI: ffffffff816b564e RDI: 0000000000000005
RBP: ffff880185646640 R08: ffff8801ac9ce080 R09: ffffed003b605aa8
R10: ffffed003b605aa8 R11: ffff8801db02d547 R12: ffffed0030ac8cb0
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000001
FS: 00007f5aba9cc700(0000) GS:ffff8801db100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000006fe178 CR3: 000000018e1fb000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
smp_call_function_many+0x870/0xa20 kernel/smp.c:434
smp_call_function kernel/smp.c:492 [inline]
on_each_cpu+0x46/0x1d0 kernel/smp.c:602
text_poke_bp+0xb9/0x158 arch/x86/kernel/alternative.c:796
__jump_label_transform.isra.0+0x43c/0x890 arch/x86/kernel/jump_label.c:102
arch_jump_label_transform+0x2f/0x40 arch/x86/kernel/jump_label.c:110
__jump_label_update+0x16e/0x1a0 kernel/jump_label.c:375
jump_label_update+0x151/0x2e0 kernel/jump_label.c:760
__static_key_slow_dec_cpuslocked+0xb0/0x200 kernel/jump_label.c:205
__static_key_slow_dec kernel/jump_label.c:215 [inline]
static_key_slow_dec+0x63/0xa0 kernel/jump_label.c:229
tracepoint_remove_func kernel/tracepoint.c:252 [inline]
tracepoint_probe_unregister+0x704/0x8c0 kernel/tracepoint.c:323
trace_event_reg+0x10c/0x350 kernel/trace/trace_events.c:309
perf_trace_event_unreg.isra.3+0xbb/0x210
kernel/trace/trace_event_perf.c:156
perf_trace_destroy+0xc1/0x100 kernel/trace/trace_event_perf.c:237
tp_perf_event_destroy+0x15/0x20 kernel/events/core.c:8314
_free_event+0x3ff/0x13b0 kernel/events/core.c:4445
put_event+0x48/0x60 kernel/events/core.c:4528
perf_event_release_kernel+0x8bd/0xf90 kernel/events/core.c:4634
perf_release+0x37/0x50 kernel/events/core.c:4644
__fput+0x34d/0x890 fs/file_table.c:209
____fput+0x15/0x20 fs/file_table.c:243
task_work_run+0x1e4/0x290 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x1aee/0x2730 kernel/exit.c:865
do_group_exit+0x16f/0x430 kernel/exit.c:968
get_signal+0x886/0x1960 kernel/signal.c:2469
do_signal+0x98/0x2040 arch/x86/kernel/signal.c:810
exit_to_usermode_loop+0x28a/0x310 arch/x86/entry/common.c:162
prepare_exit_to_usermode arch/x86/entry/common.c:196 [inline]
syscall_return_slowpath arch/x86/entry/common.c:265 [inline]
do_syscall_64+0x792/0x9d0 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x455319
RSP: 002b:00007f5aba9cbce8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 000000000072bf80 RCX: 0000000000455319
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000072bf80
RBP: 000000000072bf80 R08: 0000000000000000 R09: 000000000072bf58
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffc1dbc91f R14: 00007f5aba9cc9c0 R15: 0000000000000001
Code: c1 e8 03 4c 01 e8 c6 00 f8 48 89 44 24 28 e8 48 d4 0b 00 45 85 e4 74
6a 48 8b 44 24 28 48 83 c3 18 49 89 c4 e8 22 d3 0b 00 f3 90 <48> 89 d8 41
c6 04 24 04 48 c1 e8 03 42 0f b6 04 28 84 c0 74 08


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream

syzbot

unread,
Mar 8, 2019, 10:03:04 PM3/8/19
to syzkaller-upst...@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