[v6.1] WARNING in hci_send_acl

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 909ba1f1b414 Linux 6.1.90
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15f8f798980000
kernel config: https://syzkaller.appspot.com/x/.config?x=660c4d17e3d2ceeb
dashboard link: https://syzkaller.appspot.com/bug?extid=60ec88446cd0523870ee
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/5a4f1efb0858/disk-909ba1f1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5f7faf626bf2/vmlinux-909ba1f1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9d7a2826732f/Image-909ba1f1.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 8367 at kernel/workqueue.c:1441 __queue_work+0x10c8/0x136c kernel/workqueue.c:1441
Modules linked in:
CPU: 0 PID: 8367 Comm: syz-executor.1 Not tainted 6.1.90-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __queue_work+0x10c8/0x136c kernel/workqueue.c:1441
lr : __queue_work+0x10c8/0x136c kernel/workqueue.c:1441
sp : ffff800020f27260
x29: ffff800020f272a0 x28: 0000000000000008 x27: 0000000000002000
x26: ffff0000d7d8c000 x25: dfff800000000000 x24: 0000000100000000
x23: ffff0000d7d8c1c0 x22: ffff0000dc243788 x21: 1fffe0001b8486f1
x20: 00000000000b0012 x19: ffff0000e9c7cda0 x18: ffff800020f272e0
x17: ffff80001583d000 x16: ffff80000804a5d0 x15: 0000000000000002
x14: 1ffff00002b080b0 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000003ffff x10: ffff80002a38d000 x9 : ffff80000821631c
x8 : 0000000000040000 x7 : ffff8000103f24a4 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff800008215170
x2 : ffff0000e9c7cda0 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
__queue_work+0x10c8/0x136c kernel/workqueue.c:1441
queue_work_on+0xc0/0x16c kernel/workqueue.c:1548
queue_work include/linux/workqueue.h:512 [inline]
hci_send_acl+0x904/0xc48 net/bluetooth/hci_core.c:3268
l2cap_do_send+0x238/0x350
l2cap_chan_send+0x190c/0x1e5c
l2cap_sock_sendmsg+0x184/0x2a8 net/bluetooth/l2cap_sock.c:1162
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
____sys_sendmsg+0x55c/0x848 net/socket.c:2514
___sys_sendmsg net/socket.c:2568 [inline]
__sys_sendmmsg+0x318/0x7d8 net/socket.c:2654
__do_sys_sendmmsg net/socket.c:2683 [inline]
__se_sys_sendmmsg net/socket.c:2680 [inline]
__arm64_sys_sendmmsg+0xa0/0xbc net/socket.c:2680
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 5966
hardirqs last enabled at (5965): [<ffff800012238ed4>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (5965): [<ffff800012238ed4>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (5966): [<ffff800008215164>] queue_work_on+0x7c/0x16c kernel/workqueue.c:1545
softirqs last enabled at (5956): [<ffff8000103c1cdc>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last enabled at (5956): [<ffff8000103c1cdc>] release_sock+0x178/0x1cc net/core/sock.c:3511
softirqs last disabled at (5954): [<ffff8000103c1ba0>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (5954): [<ffff8000103c1ba0>] release_sock+0x3c/0x1cc net/core/sock.c:3498
---[ 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 syzk...@googlegroups.com.

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