[v6.1] WARNING in delayed_work_timer_fn (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0bc96de781b4 Linux 6.1.148
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14b00234580000
kernel config: https://syzkaller.appspot.com/x/.config?x=483f799cd9933afc
dashboard link: https://syzkaller.appspot.com/bug?extid=8aa7ee597d79feab5ef8
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cd15350f801a/disk-0bc96de7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/789a5d74139d/vmlinux-0bc96de7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a1ef0a7e815a/Image-0bc96de7.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4461 at kernel/workqueue.c:1441 __queue_work+0xf9c/0x123c kernel/workqueue.c:1441
Modules linked in:
CPU: 0 PID: 4461 Comm: syz.4.11 Not tainted 6.1.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 424000c5 (nZcv daIF +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __queue_work+0xf9c/0x123c kernel/workqueue.c:1441
lr : __queue_work+0xf9c/0x123c kernel/workqueue.c:1441
sp : ffff800008007b30
x29: ffff800008007b70 x28: 1fffe0001a69b001 x27: 0000000000000008
x26: ffff700001000f84 x25: dfff800000000000 x24: ffff0000d600f800
x23: ffff0000d600f9c0 x22: ffff0000d34d8008 x21: 1fffe0001a69b001
x20: 00000000000b0012 x19: ffff0000d2678bc0 x18: 0000000000000000
x17: ffff80018a6c9000 x16: ffff8000082d2410 x15: 0000000000010001
x14: 00000000ffff8000 x13: 1ffff00002a160b1 x12: 0000000000ff0100
x11: ff008000081f1d7c x10: 0000000000000000 x9 : ffff8000081f1d7c
x8 : ffff0000d34d8000 x7 : ffff8000083af824 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff800013acae40
x2 : ffff0000d2678bc0 x1 : 0000000000000100 x0 : 0000000000000000
Call trace:
__queue_work+0xf9c/0x123c kernel/workqueue.c:1441
delayed_work_timer_fn+0x74/0x90 kernel/workqueue.c:1646
call_timer_fn+0x1b8/0x964 kernel/time/timer.c:1504
expire_timers kernel/time/timer.c:1544 [inline]
__run_timers+0x490/0x6bc kernel/time/timer.c:1820
run_timer_softirq+0x7c/0x114 kernel/time/timer.c:1833
handle_softirqs+0x318/0xc6c kernel/softirq.c:596
__do_softirq+0x14/0x20 kernel/softirq.c:630
____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:80
call_on_irq_stack+0x24/0x30 arch/arm64/kernel/entry.S:849
do_softirq_own_stack+0x20/0x2c arch/arm64/kernel/irq.c:85
invoke_softirq kernel/softirq.c:477 [inline]
__irq_exit_rcu+0x23c/0x43c kernel/softirq.c:679
irq_exit_rcu+0x14/0x84 kernel/softirq.c:691
__el1_irq arch/arm64/kernel/entry-common.c:472 [inline]
el1_interrupt+0x38/0x54 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+0x24c/0x644 kernel/locking/lockdep.c:5665
__mutex_lock_common+0x190/0x1f38 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
__unix_dgram_recvmsg+0x16c/0xae8 net/unix/af_unix.c:2448
unix_dgram_recvmsg+0xd0/0xe8 net/unix/af_unix.c:2548
sock_recvmsg_nosec net/socket.c:1022 [inline]
____sys_recvmsg+0x62c/0x71c net/socket.c:2736
___sys_recvmsg net/socket.c:2780 [inline]
do_recvmmsg+0x364/0x96c net/socket.c:2874
__sys_recvmmsg net/socket.c:2953 [inline]
__do_sys_recvmmsg net/socket.c:2976 [inline]
__se_sys_recvmmsg net/socket.c:2969 [inline]
__arm64_sys_recvmmsg+0x17c/0x238 net/socket.c:2969
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 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: 95989
hardirqs last enabled at (95988): [<ffff8000081a8d58>] handle_softirqs+0x1e0/0xc6c kernel/softirq.c:580
hardirqs last disabled at (95989): [<ffff800011a34484>] __raw_spin_lock_irq include/linux/spinlock_api_smp.h:117 [inline]
hardirqs last disabled at (95989): [<ffff800011a34484>] _raw_spin_lock_irq+0x34/0x9c kernel/locking/spinlock.c:170
softirqs last enabled at (90340): [<ffff8000081a9670>] softirq_handle_end kernel/softirq.c:439 [inline]
softirqs last enabled at (90340): [<ffff8000081a9670>] handle_softirqs+0xaf8/0xc6c kernel/softirq.c:624
softirqs last disabled at (95987): [<ffff800008020164>] __do_softirq+0x14/0x20 kernel/softirq.c:630
---[ 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