BUG: soft lockup in smp_call_function_single (2)

17 views
Skip to first unread message

syzbot

unread,
Sep 10, 2018, 3:31:05 AM9/10/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 9a5682765a2e Merge branch 'x86-urgent-for-linus' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14111221400000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f59875069d721b6
dashboard link: https://syzkaller.appspot.com/bug?extid=0a724a69085bd4b42e35
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
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+0a724a...@syzkaller.appspotmail.com

watchdog: BUG: soft lockup - CPU#0 stuck for 123s! [syz-executor0:8009]
Modules linked in:
irq event stamp: 32790
hardirqs last enabled at (32789): [<ffffffff81007d91>]
trace_hardirqs_on_thunk+0x1a/0x1c
hardirqs last disabled at (32790): [<ffffffff81007dad>]
trace_hardirqs_off_thunk+0x1a/0x1c
softirqs last enabled at (4938): [<ffffffff87e007ba>]
__do_softirq+0x7ba/0xad8 kernel/softirq.c:318
softirqs last disabled at (4873): [<ffffffff814ab9ff>] invoke_softirq
kernel/softirq.c:372 [inline]
softirqs last disabled at (4873): [<ffffffff814ab9ff>] irq_exit+0x17f/0x1c0
kernel/softirq.c:412
CPU: 0 PID: 8009 Comm: syz-executor0 Not tainted 4.19.0-rc2+ #230
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:check_kcov_mode kernel/kcov.c:67 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x20/0x50 kernel/kcov.c:101
Code: 4c d8 20 4c 89 08 5d c3 66 90 55 48 89 e5 65 48 8b 04 25 40 ee 01 00
65 8b 15 fc 1c 83 7e 81 e2 00 01 1f 00 48 8b 75 08 75 2b <8b> 90 d0 12 00
00 83 fa 02 75 20 48 8b 88 d8 12 00 00 8b 80 d4 12
RSP: 0018:ffff8801b9257390 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: ffff8801940f4580 RBX: ffff8801b9257418 RCX: ffffffff817284a9
RDX: 0000000000000000 RSI: ffffffff81728458 RDI: 0000000000000005
RBP: ffff8801b9257390 R08: ffff8801940f4580 R09: ffffed003b5e5ba0
R10: ffffed003b5e5ba0 R11: ffff8801daf2dd07 R12: ffffed003724ae90
R13: 1ffff1003724ae7c R14: dffffc0000000000 R15: 0000000000000001
FS: 000000000124c940(0000) GS:ffff8801dae00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020fea800 CR3: 00000001c17e1000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
rep_nop arch/x86/include/asm/processor.h:665 [inline]
cpu_relax arch/x86/include/asm/processor.h:670 [inline]
csd_lock_wait kernel/smp.c:108 [inline]
smp_call_function_single+0x258/0x660 kernel/smp.c:302
loaded_vmcs_clear arch/x86/kvm/vmx.c:2218 [inline]
vmx_vcpu_load+0x8a7/0x1030 arch/x86/kvm/vmx.c:3062
kvm_arch_vcpu_load+0x247/0x970 arch/x86/kvm/x86.c:3106
vcpu_load+0x35/0x70 arch/x86/kvm/../../../virt/kvm/kvm_main.c:164
kvm_unload_vcpu_mmu arch/x86/kvm/x86.c:8870 [inline]
kvm_free_vcpus arch/x86/kvm/x86.c:8885 [inline]
kvm_arch_destroy_vm+0x1f9/0x7c0 arch/x86/kvm/x86.c:8985
kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:752 [inline]
kvm_put_kvm+0x6c8/0xff0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:773
kvm_vcpu_release+0x7b/0xa0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2407
__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_64+0x6be/0x820 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x410c51
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 34 19 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:0000000000a3fdc0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000006 RCX: 0000000000410c51
RDX: 0000000000000000 RSI: 0000000000730f10 RDI: 0000000000000005
RBP: 0000000000000000 R08: ffffffffffffffff R09: ffffffffffffffff
R10: 0000000000a3fcf0 R11: 0000000000000293 R12: 0000000000000007
R13: 0000000000123610 R14: 0000000000000323 R15: badc0ffeebadface
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 8029 Comm: syz-executor4 Not tainted 4.19.0-rc2+ #230
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:vmx_read_guest_seg_ar+0x1ff/0x270 arch/x86/kvm/vmx.c:2554
Code: f3 fe ff ff e8 02 9d 62 00 48 8d 04 5b 49 8d bc c4 0c 5a 00 00 48 b8
00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 0f b6 14 02 <48> 89 f8 83 e0
07 83 c0 03 38 d0 7c 04 84 d2 75 31 48 8d 04 5b 45
RSP: 0018:ffff8801c020edf0 EFLAGS: 00000807
RAX: dffffc0000000000 RBX: 0000000000000002 RCX: ffffffff811c33b0
RDX: 0000000000000000 RSI: ffffffff811c33be RDI: ffff8801c757eafc
RBP: ffff8801c020ee18 R08: ffff8801c88a04c0 R09: fffff520026ac047
R10: fffff520026ac047 R11: ffffc9001356023b R12: ffff8801c75790c0
R13: 0000000000000800 R14: 0000000000000800 R15: 0000000000100000
FS: 00007fae23f34700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31d25000 CR3: 00000001bf9be000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
vmx_get_cpl+0x5b/0x90 arch/x86/kvm/vmx.c:5492
kvm_arch_vcpu_put+0x9b/0x420 arch/x86/kvm/x86.c:3163
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+0x43/0x70 include/linux/rcupdate.h:630
get_mem_cgroup_from_mm+0x8c/0x440 mm/memcontrol.c:834
get_mem_cgroup_from_current mm/memcontrol.c:890 [inline]
memcg_kmem_get_cache+0x1fc/0x9d0 mm/memcontrol.c:2537
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
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457099
Code: fd b4 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 cb b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fae23f33c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fae23f346d4 RCX: 0000000000457099
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
RBP: 00000000009300a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004cf730 R14: 00000000004c59b9 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,
Mar 8, 2019, 8:12:05 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