[syzbot] [bluetooth?] WARNING in sco_conn_put

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    d3c9510dc900 net: page_pool: rename page_pool_is_last_ref()
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17efd730580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=87a291e9e8ffbb16
dashboard link: https://syzkaller.appspot.com/bug?extid=b1f28526bea4dce0f04f
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/4e4dd3da989d/disk-d3c9510d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fd16db384609/vmlinux-d3c9510d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7903aba8a210/bzImage-d3c9510d.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b1f28526bea4dce0f04f@xxxxxxxxxxxxxxxxxxxxxxxxx

------------[ cut here ]------------
WARNING: CPU: 1 PID: 8522 at kernel/workqueue.c:2257 __queue_work+0xcd3/0xf50 kernel/workqueue.c:2256
Modules linked in:
CPU: 1 UID: 0 PID: 8522 Comm: syz.1.688 Not tainted 6.13.0-rc2-syzkaller-00457-gd3c9510dc900 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
RIP: 0010:__queue_work+0xcd3/0xf50 kernel/workqueue.c:2256
Code: ff e8 71 e8 37 00 90 0f 0b 90 e9 b2 fe ff ff e8 63 e8 37 00 eb 13 e8 5c e8 37 00 eb 0c e8 55 e8 37 00 eb 05 e8 4e e8 37 00 90 <0f> 0b 90 48 83 c4 60 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc
RSP: 0018:ffffc9000485f888 EFLAGS: 00010087
RAX: ffffffff816775e4 RBX: ffff88802abf1e00 RCX: 0000000000080000
RDX: ffffc90005282000 RSI: 00000000000002f5 RDI: 00000000000002f6
RBP: 0000000000000000 R08: ffffffff81676a44 R09: 0000000000000000
R10: ffffc9000485f960 R11: fffff5200090bf2d R12: ffff88805a00d800
R13: ffff88805a00d9c0 R14: dffffc0000000000 R15: 0000000000000008
FS:  00007fbe34d8a6c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c352926 CR3: 0000000028684000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 queue_delayed_work_on+0x1ca/0x390 kernel/workqueue.c:2552
 sco_conn_free net/bluetooth/sco.c:91 [inline]
 kref_put include/linux/kref.h:65 [inline]
 sco_conn_put+0x145/0x210 net/bluetooth/sco.c:107
 sco_chan_del+0xa3/0x180 net/bluetooth/sco.c:236
 sco_sock_close net/bluetooth/sco.c:526 [inline]
 sco_sock_release+0xb3/0x320 net/bluetooth/sco.c:1300
 __sock_release net/socket.c:640 [inline]
 sock_close+0xbc/0x240 net/socket.c:1419
 __fput+0x23c/0xa50 fs/file_table.c:450
 task_work_run+0x24f/0x310 kernel/task_work.c:239
 get_signal+0x15f7/0x1750 kernel/signal.c:2790
 arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:337
 exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
 exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
 syscall_exit_to_user_mode+0xce/0x340 kernel/entry/common.c:218
 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fbe33f85d29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbe34d8a038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: fffffffffffffffc RBX: 00007fbe34175fa0 RCX: 00007fbe33f85d29
RDX: 0000000000000008 RSI: 0000000020000000 RDI: 0000000000000004
RBP: 00007fbe34001a20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fbe34175fa0 R15: 00007ffe3e4f91f8
 </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