[v6.1] WARNING in delayed_work_timer_fn (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e7cddbb41b63 Linux 6.1.67
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10b4f06ce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4d75c4ebe0b479d3
dashboard link: https://syzkaller.appspot.com/bug?extid=fe0cb085668a18e84358
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/e225d33f0758/disk-e7cddbb4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1f23e16b249c/vmlinux-e7cddbb4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0947ed4da17a/Image-e7cddbb4.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 14485 at kernel/workqueue.c:1441 __queue_work+0x10c8/0x136c kernel/workqueue.c:1441
Modules linked in:
CPU: 1 PID: 14485 Comm: syz-executor.4 Not tainted 6.1.67-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
pstate: 004000c5 (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 : ffff800008017b70
x29: ffff800008017bb0 x28: 0000000000000008 x27: dfff800000000000
x26: ffff0000cdafa000 x25: dfff800000000000 x24: 0000000000000100
x23: ffff0000cdafa1c0 x22: ffff0000c8ac5348 x21: 1fffe00019158a69
x20: 00000000000b0012 x19: ffff0000ce2d8bc0 x18: ffff80001ef37420
x17: ffff80019ec10000 x16: ffff800012141a14 x15: 0000000000010000
x14: 1ffff00002b040b0 x13: dfff800000000000 x12: 00000000282b313f
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800008215fb0
x8 : ffff0000c8ac5340 x7 : ffff8000083fc184 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff80001426ff00
x2 : ffff0000ce2d8bc0 x1 : 0000000000000100 x0 : 0000000000000000
Call trace:
__queue_work+0x10c8/0x136c kernel/workqueue.c:1441
delayed_work_timer_fn+0x74/0x90 kernel/workqueue.c:1646
call_timer_fn+0x1c0/0xa1c kernel/time/timer.c:1474
expire_timers kernel/time/timer.c:1514 [inline]
__run_timers+0x584/0x718 kernel/time/timer.c:1790
run_timer_softirq+0x7c/0x114 kernel/time/timer.c:1803
__do_softirq+0x314/0xe38 kernel/softirq.c:571
____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:79
call_on_irq_stack+0x24/0x4c arch/arm64/kernel/entry.S:893
do_softirq_own_stack+0x20/0x2c arch/arm64/kernel/irq.c:84
invoke_softirq kernel/softirq.c:452 [inline]
__irq_exit_rcu+0x264/0x4d4 kernel/softirq.c:650
irq_exit_rcu+0x14/0x84 kernel/softirq.c:662
__el1_irq arch/arm64/kernel/entry-common.c:472 [inline]
el1_interrupt+0x38/0x68 arch/arm64/kernel/entry-common.c:486
el1h_64_irq_handler+0x18/0x24 arch/arm64/kernel/entry-common.c:491
el1h_64_irq+0x64/0x68 arch/arm64/kernel/entry.S:581
arch_local_irq_restore arch/arm64/include/asm/irqflags.h:122 [inline]
lock_acquire+0x2ac/0x7cc kernel/locking/lockdep.c:5665
__flush_workqueue+0x14c/0x11c4 kernel/workqueue.c:2812
drain_workqueue+0xb8/0x32c kernel/workqueue.c:2977
hci_dev_close_sync+0x38c/0xf1c net/bluetooth/hci_sync.c:4960
hci_dev_do_close net/bluetooth/hci_core.c:554 [inline]
hci_unregister_dev+0x1e8/0x4ac net/bluetooth/hci_core.c:2736
vhci_release+0x7c/0xcc drivers/bluetooth/hci_vhci.c:571
__fput+0x30c/0x7bc fs/file_table.c:320
____fput+0x20/0x30 fs/file_table.c:348
task_work_run+0x240/0x2f0 kernel/task_work.c:179
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0x554/0x1a88 kernel/exit.c:869
do_group_exit+0x194/0x22c kernel/exit.c:1019
__do_sys_exit_group kernel/exit.c:1030 [inline]
__se_sys_exit_group kernel/exit.c:1028 [inline]
__wake_up_parent+0x0/0x60 kernel/exit.c:1028
__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: 180701
hardirqs last enabled at (180700): [<ffff800012221dcc>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (180700): [<ffff800012221dcc>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (180701): [<ffff800012221c2c>] __raw_spin_lock_irq include/linux/spinlock_api_smp.h:117 [inline]
hardirqs last disabled at (180701): [<ffff800012221c2c>] _raw_spin_lock_irq+0x34/0x9c kernel/locking/spinlock.c:170
softirqs last enabled at (179924): [<ffff800008020d7c>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (179924): [<ffff800008020d7c>] __do_softirq+0xc1c/0xe38 kernel/softirq.c:600
softirqs last disabled at (180687): [<ffff80000802a99c>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:79
---[ 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