BUG: soft lockup in perf_release

9 views
Skip to first unread message

syzbot

unread,
Sep 17, 2018, 5:23:05 PM9/17/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 27c5a778dfe2 Merge branch 'x86-urgent-for-linus' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15cda8c9400000
kernel config: https://syzkaller.appspot.com/x/.config?x=9c4a80625153107e
dashboard link: https://syzkaller.appspot.com/bug?extid=bb4935a5c09b5ff79940
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
userspace arch: i386
CC: [fred...@kernel.org linux-...@vger.kernel.org
mi...@kernel.org tg...@linutronix.de]

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

watchdog: BUG: soft lockup - CPU#0 stuck for 123s! [syz-executor1:14137]
Modules linked in:
irq event stamp: 70240
hardirqs last enabled at (70239): [<ffffffff81007d91>]
trace_hardirqs_on_thunk+0x1a/0x1c
hardirqs last disabled at (70240): [<ffffffff81007dad>]
trace_hardirqs_off_thunk+0x1a/0x1c
softirqs last enabled at (17270): [<ffffffff87e007ba>]
__do_softirq+0x7ba/0xad8 kernel/softirq.c:318
softirqs last disabled at (17205): [<ffffffff814ab9ff>] invoke_softirq
kernel/softirq.c:372 [inline]
softirqs last disabled at (17205): [<ffffffff814ab9ff>]
irq_exit+0x17f/0x1c0 kernel/softirq.c:412
CPU: 0 PID: 14137 Comm: syz-executor1 Not tainted 4.19.0-rc3+ #142
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:rep_nop arch/x86/include/asm/processor.h:665 [inline]
RIP: 0010:cpu_relax arch/x86/include/asm/processor.h:670 [inline]
RIP: 0010:csd_lock_wait kernel/smp.c:108 [inline]
RIP: 0010:smp_call_function_single+0x25a/0x660 kernel/smp.c:302
Code: e8 03 4c 01 f0 c6 00 f8 48 89 44 24 28 e8 8e 4d 0c 00 45 85 e4 74 67
48 8b 44 24 28 48 83 c3 18 49 89 c4 e8 68 4c 0c 00 f3 90 <48> 89 d8 41 c6
04 24 04 48 c1 e8 03 42 0f b6 04 30 84 c0 74 08 3c
RSP: 0018:ffff88019117f420 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: ffff88019112c080 RBX: ffff88019117f498 RCX: ffffffff81728839
RDX: 0000000000000000 RSI: ffffffff817287e8 RDI: 0000000000000005
RBP: ffff88019117f570 R08: ffff88019112c080 R09: ffffed003b5e5ba0
R10: ffffed003b5e5ba0 R11: ffff8801daf2dd07 R12: ffffed003222fea0
R13: 1ffff1003222fe8c R14: dffffc0000000000 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8801dae00000(0063) knlGS:0000000008be8900
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00000000f5ebedb0 CR3: 00000001d929b000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
task_function_call+0x189/0x280 kernel/events/core.c:115
event_function_call+0x305/0x600 kernel/events/core.c:277
perf_remove_from_context+0xa3/0x1d0 kernel/events/core.c:2105
perf_event_release_kernel+0x295/0xfa0 kernel/events/core.c:4555
perf_release+0x37/0x50 kernel/events/core.c:4642
__fput+0x385/0xa30 fs/file_table.c:278
____fput+0x15/0x20 fs/file_table.c:309
task_work_run+0x1e8/0x2a0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x318/0x380 arch/x86/entry/common.c:166
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_32_irqs_on arch/x86/entry/common.c:341 [inline]
do_fast_syscall_32+0xcd5/0xfb2 arch/x86/entry/common.c:397
entry_SYSENTER_compat+0x70/0x7f arch/x86/entry/entry_64_compat.S:139
RIP: 0023:0xf7f25ca9
Code: 85 d2 74 02 89 0a 5b 5d c3 8b 04 24 c3 8b 0c 24 c3 8b 1c 24 c3 90 90
90 90 90 90 90 90 90 90 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90
90 90 90 eb 0d 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 002b:000000000845fdac EFLAGS: 00000216 ORIG_RAX: 0000000000000006
RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000
RDX: 0000000000000004 RSI: 0000000000000010 RDI: 0000000000000000
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 14163 Comm: syz-executor0 Not tainted 4.19.0-rc3+ #142
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:native_set_debugreg+0x31/0x40 arch/x86/include/asm/debugreg.h:74
Code: 77 2d 89 ff 48 8b 04 fd a0 da 07 88 e9 28 96 aa 06 0f 23 fe 5d c3 0f
23 c6 5d c3 0f 23 ce 5d c3 0f 23 d6 5d c3 0f 23 de 5d c3 <0f> 23 f6 5d c3
0f 0b 0f 1f 84 00 00 00 00 00 55 83 ff 07 48 89 e5
RSP: 0018:ffff880195c26fb0 EFLAGS: 00000097
RAX: ffffffff8135d9f1 RBX: ffff880190538180 RCX: 1ffff100320a78b7
RDX: 0000000040000002 RSI: 0000000000000000 RDI: 0000000000000006
RBP: ffff880195c26fb0 R08: ffff8801bf7485c0 R09: fffff52001dc5247
R10: fffff52001dc5247 R11: ffffc9000ee2923b R12: ffffffff89171000
R13: 0000000000000000 R14: ffffc9000ee297e0 R15: ffff8801bf7485c0
FS: 0000000000000000(0000) GS:ffff8801daf00000(0063) knlGS:00000000f5f7eb40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00007fc794aac6f0 CR3: 00000001c79b4000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
set_debugreg arch/x86/include/asm/paravirt.h:42 [inline]
kvm_arch_vcpu_put+0x2ef/0x420 arch/x86/kvm/x86.c:3189
kvm_sched_out+0x91/0xb0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3985
__fire_sched_out_preempt_notifiers kernel/sched/core.c:2497 [inline]
fire_sched_out_preempt_notifiers kernel/sched/core.c:2505 [inline]
prepare_task_switch kernel/sched/core.c:2611 [inline]
context_switch kernel/sched/core.c:2790 [inline]
__schedule+0xf8c/0x1ed0 kernel/sched/core.c:3473
preempt_schedule_notrace+0x70/0x130 kernel/sched/core.c:3671
___preempt_schedule_notrace+0x16/0x31
rcu_is_watching+0x23/0x30 kernel/rcu/tree.c:1026
rcu_read_lock_held+0x87/0xc0 kernel/rcu/update.c:281
cache_from_memcg_idx mm/slab.h:255 [inline]
memcg_kmem_get_cache+0x758/0x9d0 mm/memcontrol.c:2542
slab_pre_alloc_hook mm/slab.h:428 [inline]
slab_alloc mm/slab.c:3378 [inline]
kmem_cache_alloc+0x193/0x730 mm/slab.c:3552
kmem_cache_zalloc include/linux/slab.h:697 [inline]
mmu_topup_memory_cache arch/x86/kvm/mmu.c:917 [inline]
mmu_topup_memory_caches+0x2ec/0x390 arch/x86/kvm/mmu.c:970
kvm_mmu_load+0x21/0xfa0 arch/x86/kvm/mmu.c:4952
kvm_mmu_reload arch/x86/kvm/mmu.h:86 [inline]
vcpu_enter_guest+0x3dee/0x62e0 arch/x86/kvm/x86.c:7513
vcpu_run arch/x86/kvm/x86.c:7711 [inline]
kvm_arch_vcpu_ioctl_run+0x375/0x16e0 arch/x86/kvm/x86.c:7888
kvm_vcpu_ioctl+0x72b/0x1150 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2590
kvm_vcpu_compat_ioctl+0x210/0x4a0
arch/x86/kvm/../../../virt/kvm/kvm_main.c:2785
__do_compat_sys_ioctl fs/compat_ioctl.c:1419 [inline]
__se_compat_sys_ioctl fs/compat_ioctl.c:1365 [inline]
__ia32_compat_sys_ioctl+0x20e/0x630 fs/compat_ioctl.c:1365
do_syscall_32_irqs_on arch/x86/entry/common.c:326 [inline]
do_fast_syscall_32+0x34d/0xfb2 arch/x86/entry/common.c:397
entry_SYSENTER_compat+0x70/0x7f arch/x86/entry/entry_64_compat.S:139
RIP: 0023:0xf7f82ca9
Code: 85 d2 74 02 89 0a 5b 5d c3 8b 04 24 c3 8b 0c 24 c3 8b 1c 24 c3 90 90
90 90 90 90 90 90 90 90 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90
90 90 90 eb 0d 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 002b:00000000f5f7e0cc EFLAGS: 00000296 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 000000000000ae80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000


---
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#bug-status-tracking for how to communicate with
syzbot.

syzbot

unread,
Aug 19, 2019, 3:15:03 AM8/19/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