[v5.15] WARNING: ODEBUG bug in hci_dev_do_close

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 83655231580b Linux 5.15.159
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1234c352980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c49fc0ce9b46e64b
dashboard link: https://syzkaller.appspot.com/bug?extid=742e3e5c2e19b9420d0e
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/faa8b26e9d92/disk-83655231.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dacb199b57cf/vmlinux-83655231.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d7c5b8943497/Image-83655231.gz.xz

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

------------[ cut here ]------------
ODEBUG: assert_init not available (active state 0) object type: timer_list hint: 0x0
WARNING: CPU: 0 PID: 7675 at lib/debugobjects.c:520 debug_print_object+0x148/0x1d4 lib/debugobjects.c:517
Modules linked in:
CPU: 0 PID: 7675 Comm: syz-executor.3 Not tainted 5.15.159-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 : debug_print_object+0x148/0x1d4 lib/debugobjects.c:517
lr : debug_print_object+0x148/0x1d4 lib/debugobjects.c:517
sp : ffff80001ebe7530
x29: ffff80001ebe7530 x28: dfff800000000000 x27: ffff700003d7ceb4
x26: ffff0000ccd786a8 x25: ffff8000083bc390 x24: dfff800000000000
x23: 0000000000000000 x22: 0000000000000000 x21: ffff800011f97b40
x20: ffff800011b02f60 x19: ffff800011f97680 x18: 0000000000000001
x17: 0000000000000000 x16: ffff80000833680c x15: 00000000ffffffff
x14: ffff0000efe051c0 x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : 9eb11c30c969ee00
x8 : 9eb11c30c969ee00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001ebe6c98 x4 : ffff800014a2f7a0 x3 : ffff800008336958
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000054
Call trace:
debug_print_object+0x148/0x1d4 lib/debugobjects.c:517
debug_object_assert_init+0x314/0x3c4 lib/debugobjects.c:893
debug_timer_assert_init kernel/time/timer.c:739 [inline]
debug_assert_init kernel/time/timer.c:784 [inline]
del_timer+0xa8/0x2b4 kernel/time/timer.c:1224
try_to_grab_pending+0xa4/0x66c kernel/workqueue.c:1283
__cancel_work_timer+0x118/0x548 kernel/workqueue.c:3140
cancel_delayed_work_sync+0x24/0x38 kernel/workqueue.c:3322
hci_dev_do_close+0x26c/0x1060 net/bluetooth/hci_core.c:1771
hci_unregister_dev+0x228/0x4b4 net/bluetooth/hci_core.c:4036
vhci_release+0x74/0xc4 drivers/bluetooth/hci_vhci.c:345
__fput+0x30c/0x7f0 fs/file_table.c:280
____fput+0x20/0x30 fs/file_table.c:308
task_work_run+0x130/0x1e4 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x670/0x20bc kernel/exit.c:872
do_group_exit+0x110/0x268 kernel/exit.c:994
__do_sys_exit_group kernel/exit.c:1005 [inline]
__se_sys_exit_group kernel/exit.c:1003 [inline]
__wake_up_parent+0x0/0x60 kernel/exit.c:1003
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 1506056
hardirqs last enabled at (1506055): [<ffff800011a72b0c>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:168 [inline]
hardirqs last enabled at (1506055): [<ffff800011a72b0c>] _raw_spin_unlock_irq+0x9c/0x134 kernel/locking/spinlock.c:202
hardirqs last disabled at (1506056): [<ffff800008206d10>] try_to_grab_pending+0xcc/0x66c kernel/workqueue.c:1272
softirqs last enabled at (1504448): [<ffff800008021c64>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (1504448): [<ffff800008021c64>] __do_softirq+0xb5c/0xdb0 kernel/softirq.c:587
softirqs last disabled at (1504433): [<ffff8000081b6568>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (1504433): [<ffff8000081b6568>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (1504433): [<ffff8000081b6568>] __irq_exit_rcu+0x264/0x4d4 kernel/softirq.c:637
---[ end trace 731050d10fba3c1e ]---


---
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