BUG: soft lockup in vhci_release

4 views
Skip to first unread message

syzbot

unread,
Apr 16, 2021, 8:26:23 AM4/16/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: cf256fbc Linux 4.14.231
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=133f0f65d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=403e68efdb1dcca6
dashboard link: https://syzkaller.appspot.com/bug?extid=00dd9f531c2c9cebb840

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

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+00dd9f...@syzkaller.appspotmail.com

audit: type=1800 audit(1618575917.148:34661): pid=2742 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.0" name="SYSV00000000" dev="hugetlbfs" ino=557070 res=0
audit: type=1800 audit(1618575917.488:34662): pid=2752 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.5" name="SYSV00000000" dev="hugetlbfs" ino=458760 res=0
watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [syz-executor.1:2033]
Modules linked in:
irq event stamp: 3293008
hardirqs last enabled at (3293007): [<ffffffff87400976>] restore_regs_and_return_to_kernel+0x0/0x2a
hardirqs last disabled at (3293008): [<ffffffff874018ae>] apic_timer_interrupt+0x8e/0xa0 arch/x86/entry/entry_64.S:793
softirqs last enabled at (172578): [<ffffffff8760068b>] __do_softirq+0x68b/0x9ff kernel/softirq.c:314
softirqs last disabled at (172351): [<ffffffff81320c83>] invoke_softirq kernel/softirq.c:368 [inline]
softirqs last disabled at (172351): [<ffffffff81320c83>] irq_exit+0x193/0x240 kernel/softirq.c:409
CPU: 0 PID: 2033 Comm: syz-executor.1 Not tainted 4.14.231-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88809c69c580 task.stack: ffff888065c80000
RIP: 0010:pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:411 [inline]
RIP: 0010:__pv_queued_spin_lock_slowpath+0x265/0x910 kernel/locking/qspinlock.c:465
RSP: 0018:ffff888065c876e8 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff10
RAX: 0000000000000003 RBX: ffff8880ba42ae80 RCX: fffffbfff13ba885
RDX: 0000000000004ebd RSI: 0000000000000004 RDI: 0000000000000286
RBP: ffffffff89dd442c R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
R13: dffffc0000000000 R14: ffffffff89dd442d R15: ffffed10174855d8
FS: 00007f19e8965700(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000a40 CR3: 00000000ab306000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:669 [inline]
queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:52 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:90 [inline]
queued_read_lock_slowpath+0x150/0x190 kernel/locking/qrwlock.c:90
hci_send_to_channel+0x3c/0x200 net/bluetooth/hci_sock.c:261
hci_send_monitor_ctrl_event+0x3dd/0x500 net/bluetooth/hci_sock.c:391
mgmt_send_event+0x2b3/0x330 net/bluetooth/mgmt_util.c:86
mgmt_limited_event net/bluetooth/mgmt.c:260 [inline]
new_settings net/bluetooth/mgmt.c:1089 [inline]
__mgmt_power_off+0x152/0x200 net/bluetooth/mgmt.c:6688
hci_dev_do_close+0x968/0xca0 net/bluetooth/hci_core.c:1618
hci_unregister_dev+0x17f/0x8c0 net/bluetooth/hci_core.c:3193
vhci_release+0x70/0xe0 drivers/bluetooth/hci_vhci.c:354
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa44/0x2850 kernel/exit.c:868
do_group_exit+0x100/0x2e0 kernel/exit.c:965
get_signal+0x38d/0x1ca0 kernel/signal.c:2423
do_signal+0x7c/0x1550 arch/x86/kernel/signal.c:792
exit_to_usermode_loop+0x160/0x200 arch/x86/entry/common.c:160
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x466459
RSP: 002b:00007f19e8965218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 000000000056bf68 RCX: 0000000000466459
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000000000056bf68
RBP: 000000000056bf60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf6c
R13: 00007ffd0830ab6f R14: 00007f19e8965300 R15: 0000000000022000
Code: 84 c0 0f 85 2e 04 00 00 48 89 e9 48 89 ee c6 45 01 01 ba 00 80 00 00 48 c1 e9 03 83 e6 07 41 b8 01 00 00 00 4c 01 e9 eb 0b f3 90 <83> ea 01 0f 84 42 04 00 00 0f b6 01 40 38 f0 7f 08 84 c0 0f 85
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 2761 Comm: syz-executor.3 Not tainted 4.14.231-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88806b45a200 task.stack: ffff888075cc8000
RIP: 0010:__read_once_size include/linux/compiler.h:183 [inline]
RIP: 0010:atomic_read arch/x86/include/asm/atomic.h:27 [inline]
RIP: 0010:queued_write_lock_slowpath+0xcb/0x1d0 kernel/locking/qrwlock.c:139
RSP: 0018:ffff888075ccfd38 EFLAGS: 00000206
RAX: 0000000000000101 RBX: ffffffff89dd4428 RCX: 00000000000030dc
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffff89dd4428
RBP: ffffffff89dd442c R08: ffffffff8b9a81a0 R09: 0000000000040591
R10: ffff88806b45aab0 R11: ffff88806b45a200 R12: 0000000000000003
R13: fffffbfff13ba885 R14: 00000000000000ff R15: ffffffff8863a320
FS: 000000000338a400(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000564dfcef25e0 CR3: 000000005b686000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
queued_write_lock include/asm-generic/qrwlock.h:134 [inline]
do_raw_write_lock+0xc2/0x1d0 kernel/locking/spinlock_debug.c:203
bt_sock_link+0x1f/0x120 net/bluetooth/af_bluetooth.c:143
hci_sock_create+0x15c/0x1d0 net/bluetooth/hci_sock.c:2017
bt_sock_create+0x13b/0x280 net/bluetooth/af_bluetooth.c:130
__sock_create+0x303/0x620 net/socket.c:1275
sock_create net/socket.c:1315 [inline]
SYSC_socket net/socket.c:1345 [inline]
SyS_socket+0xd1/0x1b0 net/socket.c:1325
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x467ac7
RSP: 002b:00007ffe99243588 EFLAGS: 00000206 ORIG_RAX: 0000000000000029
RAX: ffffffffffffffda RBX: 00007ffe99243c28 RCX: 0000000000467ac7
RDX: 0000000000000001 RSI: 0000000000000003 RDI: 000000000000001f
RBP: 00007ffe992436c0 R08: 00000000004af718 R09: 00007ffe99243070
R10: 0000000000000000 R11: 0000000000000206 R12: 00000000ffffffff
R13: 000000000056ca68 R14: 0000000000000000 R15: 00000000000000f8
Code: 75 dc 49 89 dd 49 89 dc 41 be ff 00 00 00 49 c1 ed 03 41 83 e4 07 48 b8 00 00 00 00 00 fc ff df 49 01 c5 41 83 c4 03 eb 02 f3 90 <41> 0f b6 45 00 41 38 c4 7c 08 84 c0 0f 85 9e 00 00 00 8b 03 83


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

syzbot

unread,
Aug 14, 2021, 8:26:12 AM8/14/21
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