syzbot


BUG: soft lockup in hci_sock_sendmsg (2)

Status: upstream: reported C repro on 2022/05/04 08:18
Reported-by: syzbot+8e7fd0be1d8dc16daf4d@syzkaller.appspotmail.com
First crash: 774d, last: 475d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 BUG: soft lockup in hci_sock_sendmsg 2 1173d 1181d 0/1 auto-closed as invalid on 2021/07/29 20:24
Fix bisection attempts (7)
Created Duration User Patch Repo Result
2023/02/27 04:13 24m bisect fix linux-4.14.y job log (0) log
2023/01/25 16:17 24m bisect fix linux-4.14.y job log (0) log
2022/10/28 01:29 25m bisect fix linux-4.14.y job log (0) log
2022/09/22 02:16 24m bisect fix linux-4.14.y job log (0) log
2022/08/23 01:50 25m bisect fix linux-4.14.y job log (0) log
2022/07/23 17:15 24m bisect fix linux-4.14.y job log (0) log
2022/06/23 16:51 23m bisect fix linux-4.14.y job log (0) log

Sample crash report:
Bluetooth: hci5 command 0x0409 tx timeout
Bluetooth: hci3 command 0x0409 tx timeout
Bluetooth: hci0 command 0x0409 tx timeout
Bluetooth: hci4 command 0x0409 tx timeout
Bluetooth: hci2 command 0x0409 tx timeout
watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [syz-executor430:10031]
Modules linked in:
irq event stamp: 9522
hardirqs last  enabled at (9521): [<ffffffff812317db>] kvm_wait arch/x86/kernel/kvm.c:600 [inline]
hardirqs last  enabled at (9521): [<ffffffff812317db>] kvm_wait+0x14b/0x240 arch/x86/kernel/kvm.c:580
hardirqs last disabled at (9522): [<ffffffff87401a1e>] apic_timer_interrupt+0x8e/0xa0 arch/x86/entry/entry_64.S:796
softirqs last  enabled at (728): [<ffffffff8760068b>] __do_softirq+0x68b/0x9ff kernel/softirq.c:314
softirqs last disabled at (461): [<ffffffff81322cf3>] invoke_softirq kernel/softirq.c:368 [inline]
softirqs last disabled at (461): [<ffffffff81322cf3>] irq_exit+0x193/0x240 kernel/softirq.c:409
CPU: 0 PID: 10031 Comm: syz-executor430 Not tainted 4.14.299-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
task: ffff8880a19823c0 task.stack: ffff8880aa398000
RIP: 0010:native_safe_halt+0xe/0x10 arch/x86/include/asm/irqflags.h:61
RSP: 0018:ffff8880aa39f960 EFLAGS: 000002c2 ORIG_RAX: ffffffffffffff10
RAX: 1ffffffff11e13dc RBX: ffffffff89dd9e2c RCX: 1ffff110143305a1
RDX: dffffc0000000000 RSI: ffff8880a1982ce8 RDI: ffff8880a1982c44
RBP: 0000000000000003 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000286
R13: dffffc0000000000 R14: ffffffff89dd9e2d R15: ffffed10174869f8
FS:  00005555572e3300(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa6cea586f8 CR3: 00000000a16a6000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 arch_safe_halt arch/x86/include/asm/paravirt.h:94 [inline]
 kvm_wait arch/x86/kernel/kvm.c:600 [inline]
 kvm_wait+0x179/0x240 arch/x86/kernel/kvm.c:580
 pv_wait arch/x86/include/asm/paravirt.h:679 [inline]
 pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:447 [inline]
 __pv_queued_spin_lock_slowpath+0x722/0x910 kernel/locking/qspinlock.c:465
 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:272
 hci_send_monitor_ctrl_event+0x3dd/0x500 net/bluetooth/hci_sock.c:402
 mgmt_send_event+0x2b3/0x330 net/bluetooth/mgmt_util.c:86
 mgmt_event net/bluetooth/mgmt.c:270 [inline]
 unblock_device+0x135/0x1f0 net/bluetooth/mgmt.c:3840
 hci_mgmt_cmd net/bluetooth/hci_sock.c:1590 [inline]
 hci_sock_sendmsg+0x175b/0x1d00 net/bluetooth/hci_sock.c:1725
 sock_sendmsg_nosec net/socket.c:646 [inline]
 sock_sendmsg+0xb5/0x100 net/socket.c:656
 sock_write_iter+0x22c/0x370 net/socket.c:925
 call_write_iter include/linux/fs.h:1780 [inline]
 new_sync_write fs/read_write.c:469 [inline]
 __vfs_write+0x44c/0x630 fs/read_write.c:482
 vfs_write+0x17f/0x4d0 fs/read_write.c:544
 SYSC_write fs/read_write.c:590 [inline]
 SyS_write+0xf2/0x210 fs/read_write.c:582
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x5e/0xd3
Code: 6b 5a fa e9 4f ff ff ff 48 89 ef e8 6d 6b 5a fa eb 93 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 0f 00 2d 94 ec 62 00 fb f4 <c3> 90 0f 1f 44 00 00 0f 00 2d 84 ec 62 00 f4 c3 90 90 41 55 41 

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/11/14 19:02 linux-4.14.y e911713e40ca 943f4cb8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: soft lockup in hci_sock_sendmsg
2022/05/24 16:51 linux-4.14.y dffb5c6ff09c fcfad4ff .config console log report syz C ci2-linux-4-14 BUG: soft lockup in hci_sock_sendmsg
2022/05/24 14:55 linux-4.14.y dffb5c6ff09c fcfad4ff .config console log report info ci2-linux-4-14 BUG: soft lockup in hci_sock_sendmsg
2022/05/04 08:17 linux-4.14.y e3a56aaade89 dc9e5259 .config console log report info ci2-linux-4-14 BUG: soft lockup in hci_sock_sendmsg
* Struck through repros no longer work on HEAD.