BUG: soft lockup in perf_release

9 views
Skip to first unread message

syzbot

unread,
Aug 10, 2019, 11:19:06 AM8/10/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 893af1c7 Linux 4.19.66
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14cef9c2600000
kernel config: https://syzkaller.appspot.com/x/.config?x=d5fac5a8617b8643
dashboard link: https://syzkaller.appspot.com/bug?extid=12baff53018daa9fcebf
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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+12baff...@syzkaller.appspotmail.com

watchdog: BUG: soft lockup - CPU#1 stuck for 123s! [syz-executor.5:11265]
Modules linked in:
irq event stamp: 31360
hardirqs last enabled at (31359): [<ffffffff810065e3>]
trace_hardirqs_on_thunk+0x1a/0x1c
hardirqs last disabled at (31360): [<ffffffff810065ff>]
trace_hardirqs_off_thunk+0x1a/0x1c
softirqs last enabled at (2542): [<ffffffff87200633>]
__do_softirq+0x633/0x921 kernel/softirq.c:318
softirqs last disabled at (2453): [<ffffffff81408510>] invoke_softirq
kernel/softirq.c:372 [inline]
softirqs last disabled at (2453): [<ffffffff81408510>] irq_exit+0x180/0x1d0
kernel/softirq.c:412
CPU: 1 PID: 11265 Comm: syz-executor.5 Not tainted 4.19.66 #40
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__sanitizer_cov_trace_const_cmp4+0x16/0x20 kernel/kcov.c:190
Code: 48 89 e5 48 8b 4d 08 e8 d8 fe ff ff 5d c3 66 0f 1f 44 00 00 55 89 f2
89 fe bf 05 00 00 00 48 89 e5 48 8b 4d 08 e8 ba fe ff ff <5d> c3 0f 1f 84
00 00 00 00 00 55 48 89 f2 48 89 fe bf 07 00 00 00
RSP: 0018:ffff888032a476d0 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000000 RBX: 1ffff11006548ee0 RCX: ffffffff8160f80c
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000005
RBP: ffff888032a476d0 R08: ffff88805449a280 R09: ffffed1015d05c81
R10: ffffed1015d05c80 R11: ffff8880ae82e407 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
FS: 000000000157e940(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7a4b418028 CR3: 000000005a870000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
csd_lock_wait kernel/smp.c:108 [inline]
smp_call_function_single+0x14c/0x420 kernel/smp.c:302
smp_call_function_many+0x75f/0x8e0 kernel/smp.c:434
smp_call_function+0x42/0x90 kernel/smp.c:492
on_each_cpu+0x31/0x200 kernel/smp.c:602
text_poke_bp+0x12a/0x199 arch/x86/kernel/alternative.c:836
__jump_label_transform.isra.0+0x2ca/0x4d0 arch/x86/kernel/jump_label.c:103
arch_jump_label_transform+0x31/0x50 arch/x86/kernel/jump_label.c:111
__jump_label_update+0x1e4/0x240 kernel/jump_label.c:373
jump_label_update kernel/jump_label.c:758 [inline]
jump_label_update+0x186/0x310 kernel/jump_label.c:737
__static_key_slow_dec_cpuslocked+0x5c/0x150 kernel/jump_label.c:203
__static_key_slow_dec kernel/jump_label.c:213 [inline]
static_key_slow_dec+0x60/0xa0 kernel/jump_label.c:227
tracepoint_remove_func kernel/tracepoint.c:298 [inline]
tracepoint_probe_unregister+0x4e9/0x670 kernel/tracepoint.c:368
trace_event_reg+0x189/0x350 kernel/trace/trace_events.c:310
perf_trace_event_unreg.isra.0+0xb6/0x220
kernel/trace/trace_event_perf.c:157
perf_trace_destroy+0xbc/0x100 kernel/trace/trace_event_perf.c:238
tp_perf_event_destroy+0x16/0x20 kernel/events/core.c:8402
_free_event+0x354/0x1220 kernel/events/core.c:4453
put_event+0x47/0x60 kernel/events/core.c:4547
perf_event_release_kernel+0x6d1/0xd80 kernel/events/core.c:4662
perf_release+0x37/0x50 kernel/events/core.c:4672
__fput+0x2dd/0x8b0 fs/file_table.c:278
____fput+0x16/0x20 fs/file_table.c:309
task_work_run+0x145/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x273/0x2c0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x53d/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x413511
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48
83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48
89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffd62455fd0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 0000000000413511
RDX: 0000001b30b20000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000001 R08: 00000000f1ed4f10 R09: 00000000f1ed4f14
R10: 00007ffd624560b0 R11: 0000000000000293 R12: 000000000075bf20
R13: 00000000001b4873 R14: 00000000007613d8 R15: ffffffffffffffff
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 11256 Comm: syz-executor.0 Not tainted 4.19.66 #40
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:cpu_relax arch/x86/include/asm/processor.h:671 [inline]
RIP: 0010:mutex_spin_on_owner+0x23d/0x330 kernel/locking/mutex.c:552
Code: c3 be 08 00 00 00 4c 89 ef e8 8f 64 50 00 4c 89 e8 48 c1 e8 03 42 80
3c 30 00 0f 85 e2 00 00 00 49 8b 45 00 a8 01 75 91 f3 90 <e9> 39 fe ff ff
0f 0b e8 47 21 08 00 84 c0 0f 85 09 fe ff ff 48 c7
RSP: 0018:ffff888032ab7a90 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 1ffffffff10e48b8
RDX: 0000000000000001 RSI: 0000000000000008 RDI: 0000000000000001
RBP: ffff888032ab7ad0 R08: 1ffffffff1101198 R09: fffffbfff1101199
R10: fffffbfff1101198 R11: ffffffff88808cc7 R12: ffffed100691e420
R13: ffffffff88808cc0 R14: dffffc0000000000 R15: ffff88805449a280
FS: 0000000002113940(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000107baa8 CR3: 0000000029422000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
mutex_optimistic_spin kernel/locking/mutex.c:646 [inline]
__mutex_lock_common kernel/locking/mutex.c:928 [inline]
__mutex_lock+0x2b4/0x1300 kernel/locking/mutex.c:1072
mutex_lock_nested kernel/locking/mutex.c:1087 [inline]
atomic_dec_and_mutex_lock kernel/locking/mutex.c:1436 [inline]
atomic_dec_and_mutex_lock+0x12d/0x16a kernel/locking/mutex.c:1430
__static_key_slow_dec_cpuslocked+0x28/0x150 kernel/jump_label.c:193
__static_key_slow_dec kernel/jump_label.c:213 [inline]
static_key_slow_dec+0x60/0xa0 kernel/jump_label.c:227
preempt_notifier_dec+0x10/0x20 kernel/sched/core.c:2448
kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:759 [inline]
kvm_put_kvm+0x82e/0xc60 arch/x86/kvm/../../../virt/kvm/kvm_main.c:773
kvm_vcpu_release+0x7b/0xa0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2411
__fput+0x2dd/0x8b0 fs/file_table.c:278
____fput+0x16/0x20 fs/file_table.c:309
task_work_run+0x145/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x273/0x2c0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x53d/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x413511
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48
83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48
89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffcf0952ae0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000006 RCX: 0000000000413511
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 0000000000000001 R08: 00000000f1ed4f10 R09: 00000000f1ed4f14
R10: 00007ffcf0952bc0 R11: 0000000000000293 R12: 000000000075bf20
R13: 00000000001b4879 R14: 0000000000761538 R15: ffffffffffffffff


---
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.

syzbot

unread,
Dec 8, 2019, 9:19:06 AM12/8/19
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