Hello,
syzbot found the following issue on:
HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=177e9e24c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=650737f7e9682672
dashboard link:
https://syzkaller.appspot.com/bug?extid=bfbb27ac82ea130a7a95
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/f10713d1fd0f/disk-42616e0f.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/5a1307bb774e/vmlinux-42616e0f.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/388238a30fe4/Image-42616e0f.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+bfbb27...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 47 at net/bluetooth/hci_conn.c:646 hci_conn_timeout+0x210/0x3f4 net/bluetooth/hci_conn.c:646
Modules linked in:
CPU: 0 PID: 47 Comm: kworker/u5:0 Not tainted 6.1.15-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: hci4 hci_conn_timeout
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hci_conn_timeout+0x210/0x3f4 net/bluetooth/hci_conn.c:646
lr : hci_conn_timeout+0x210/0x3f4 net/bluetooth/hci_conn.c:646
sp : ffff80001b217b20
x29: ffff80001b217b30 x28: ffff0000d41ba400 x27: ffff0000de052250
x26: ffff0000c2ba8618 x25: 1fffe000185750c3 x24: dfff800000000000
x23: ffff0000d41ba408 x22: dfff800000000000 x21: 00000000ffffffff
x20: ffff0000de052000 x19: ffff0000de052250 x18: ffff80001b217880
x17: ffff80001141bde0 x16: ffff8000084fc844 x15: 0000000000000000
x14: 000000006cc70e04 x13: dfff800000000000 x12: 0000000000000001
x11: ff808000114205a8 x10: 0000000000000000 x9 : ffff8000114205a8
x8 : ffff0000c2a751c0 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff8000187d6000 x4 : 0000000000000008 x3 : ffff8000114203d4
x2 : 0000000000000000 x1 : 00000000ffffffff x0 : 0000000000000000
Call trace:
hci_conn_timeout+0x210/0x3f4 net/bluetooth/hci_conn.c:646
process_one_work+0x848/0x16b4 kernel/workqueue.c:2289
worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
irq event stamp: 1970
hardirqs last enabled at (1969): [<ffff8000123302d4>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline]
hardirqs last enabled at (1969): [<ffff8000123302d4>] _raw_spin_unlock_irq+0x3c/0x90 kernel/locking/spinlock.c:202
hardirqs last disabled at (1970): [<ffff80001224c56c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (0): [<ffff8000081a618c>] copy_process+0x1380/0x384c kernel/fork.c:2201
softirqs last disabled at (0): [<0000000000000000>] 0x0
---[ end trace 0000000000000000 ]---
Bluetooth: hci5: command 0x0406 tx timeout
Bluetooth: hci0: command 0x0406 tx timeout
Bluetooth: hci3: command 0x0406 tx timeout
Bluetooth: hci1: command 0x0406 tx timeout
---
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.