Hello, syzbot found the following issue on: HEAD commit: 573067a5a685 Merge branch 'for-next/core' into for-kernelci git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=10f7e0b0580000 kernel config: https://syzkaller.appspot.com/x/.config?x=cd7202b56d469648 dashboard link: https://syzkaller.appspot.com/bug?extid=afa1843ff020b481e6b5 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: arm64 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/9d3b5c855aa0/disk-573067a5.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/0c06fc1ead83/vmlinux-573067a5.xz kernel image: https://storage.googleapis.com/syzbot-assets/3390e59b9e4b/Image-573067a5.gz.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+afa1843ff020b481e6b5@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 1 PID: 6472 at kernel/workqueue.c:2257 __queue_work+0xe80/0x1308 kernel/workqueue.c:2256 Modules linked in: CPU: 1 UID: 0 PID: 6472 Comm: kworker/1:3 Not tainted 6.13.0-rc3-syzkaller-g573067a5a685 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: events l2cap_chan_timeout pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __queue_work+0xe80/0x1308 kernel/workqueue.c:2256 lr : __queue_work+0xe80/0x1308 kernel/workqueue.c:2256 sp : ffff8000a5fc7820 x29: ffff8000a5fc7870 x28: 1fffe0001b107c00 x27: 001fffffffc00001 x26: dfff800000000000 x25: ffff0000ec829800 x24: 0000000000000008 x23: 1fffe00018dfc001 x22: ffff0000ec8299c0 x21: 0000000004208060 x20: ffff0000c1080408 x19: ffff0000f131c8e8 x18: ffff8000a5fc75a0 x17: 0000000000048c2a x16: ffff800083275834 x15: 0000000000000001 x14: 1fffe0001e26391d x13: 0000000000000000 x12: 0000000000000000 x11: ffff60001e26391e x10: 0000000000ff0100 x9 : 0000000000000000 x8 : ffff0000c6fe0000 x7 : ffff800083277784 x6 : 0000000000000000 x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000 x2 : ffff0000f131c8e8 x1 : 0000000000200000 x0 : ffff0000d4acdd00 Call trace: __queue_work+0xe80/0x1308 kernel/workqueue.c:2256 (P) __queue_delayed_work+0x184/0x23c kernel/workqueue.c:2507 queue_delayed_work_on+0xec/0x1b0 kernel/workqueue.c:2552 queue_delayed_work include/linux/workqueue.h:677 [inline] hci_conn_drop+0x178/0x280 include/net/bluetooth/hci_core.h:1642 l2cap_chan_del+0x228/0x470 net/bluetooth/l2cap_core.c:674 l2cap_chan_close+0x4c8/0x82c l2cap_chan_timeout+0x128/0x288 net/bluetooth/l2cap_core.c:435 process_one_work+0x7a8/0x15cc kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x97c/0xeec kernel/workqueue.c:3391 kthread+0x288/0x310 kernel/kthread.c:389 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862 irq event stamp: 163642 hardirqs last enabled at (163641): [<ffff800080365520>] __cancel_work+0x1c4/0x29c kernel/workqueue.c:4331 hardirqs last disabled at (163642): [<ffff80008036074c>] queue_delayed_work_on+0x58/0x1b0 kernel/workqueue.c:2548 softirqs last enabled at (163636): [<ffff80008976e8b0>] spin_unlock_bh include/linux/spinlock.h:396 [inline] softirqs last enabled at (163636): [<ffff80008976e8b0>] release_sock+0x154/0x1b8 net/core/sock.c:3646 softirqs last disabled at (163634): [<ffff80008976e798>] spin_lock_bh include/linux/spinlock.h:356 [inline] softirqs last disabled at (163634): [<ffff80008976e798>] release_sock+0x3c/0x1b8 net/core/sock.c:3635 ---[ end trace 0000000000000000 ]--- --- 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 syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
