Hello, syzbot found the following issue on: HEAD commit: 2ef5971ff345 Merge tag 'vfs-6.10-rc4.fixes' of git://git.k.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=122b5b6a980000 kernel config: https://syzkaller.appspot.com/x/.config?x=fa0ce06dcc735711 dashboard link: https://syzkaller.appspot.com/bug?extid=e70cc8721ff61d6bebda compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/68c14576ffea/disk-2ef5971f.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/3e404ec95932/vmlinux-2ef5971f.xz kernel image: https://storage.googleapis.com/syzbot-assets/b486b23228a7/bzImage-2ef5971f.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+e70cc8721ff61d6bebda@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 0 PID: 9 at kernel/workqueue.c:2281 __queue_work+0xc5e/0xee0 kernel/workqueue.c:2280 Modules linked in: CPU: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.10.0-rc3-syzkaller-00021-g2ef5971ff345 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024 Workqueue: events l2cap_chan_timeout RIP: 0010:__queue_work+0xc5e/0xee0 kernel/workqueue.c:2280 Code: ff e8 46 83 36 00 90 0f 0b 90 e9 20 fd ff ff e8 38 83 36 00 eb 13 e8 31 83 36 00 eb 0c e8 2a 83 36 00 eb 05 e8 23 83 36 00 90 <0f> 0b 90 48 83 c4 58 5b 41 5c 41 5d 41 5e 41 5f 5d e9 17 9d 50 0a RSP: 0018:ffffc900000e7870 EFLAGS: 00010093 RAX: ffffffff815fa3dd RBX: ffff888015090008 RCX: ffff888016eb8000 RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000 RBP: 0000000000000020 R08: ffffffff81628b19 R09: ffffc900000e7940 R10: dffffc0000000000 R11: fffff5200001cf29 R12: ffff8880245d49c0 R13: dffffc0000000000 R14: ffff8880245d4800 R15: 0000000000000008 FS: 0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020aa3000 CR3: 000000005e458000 CR4: 0000000000350ef0 Call Trace: <TASK> queue_work_on+0x1c2/0x380 kernel/workqueue.c:2410 l2cap_send_disconn_req+0x28e/0x440 net/bluetooth/l2cap_core.c:1487 l2cap_chan_close+0x378/0x9f0 net/bluetooth/l2cap_core.c:826 l2cap_chan_timeout+0x142/0x360 net/bluetooth/l2cap_core.c:435 process_one_work kernel/workqueue.c:3231 [inline] process_scheduled_works+0xa2e/0x1830 kernel/workqueue.c:3312 worker_thread+0x86d/0xd70 kernel/workqueue.c:3393 kthread+0x2f2/0x390 kernel/kthread.c:389 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> --- 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
