[v6.1] WARNING in delayed_work_timer_fn

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1589a467c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9ccbc3d5467efd1
dashboard link: https://syzkaller.appspot.com/bug?extid=c9bfdf3d54b66f472eed
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7fe538fc87bf/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8df93997601a/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/03ad7e3bf859/Image-543aff19.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 21 at kernel/workqueue.c:1438 __queue_work+0x10c8/0x136c kernel/workqueue.c:1438
Modules linked in:
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 004000c5 (nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __queue_work+0x10c8/0x136c kernel/workqueue.c:1438
lr : __queue_work+0x10c8/0x136c kernel/workqueue.c:1438
sp : ffff800019c17910
x29: ffff800019c17950 x28: 0000000000000008 x27: dfff800000000000
x26: ffff0000c996d800 x25: dfff800000000000 x24: 0000000000000100
x23: ffff0000c996d9c0 x22: ffff0000c0a49b48 x21: 1fffe00018149369
x20: 00000000000b0012 x19: ffff00011f070250 x18: ffff800019c17700
x17: 0000000000100010 x16: ffff8000120db8f4 x15: 0000000000039cad
x14: 00000000ffffffff x13: dfff800000000000 x12: 0000000000000001
x11: ff80800008213ddc x10: 0000000000000000 x9 : ffff800008213ddc
x8 : ffff0000c0a49b40 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff800008300460
x2 : ffff00011f070250 x1 : 0000000000000100 x0 : 0000000000000000
Call trace:
__queue_work+0x10c8/0x136c kernel/workqueue.c:1438
delayed_work_timer_fn+0x74/0x90 kernel/workqueue.c:1643
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+0x30c/0xea0 kernel/softirq.c:571
run_ksoftirqd+0x68/0x258 kernel/softirq.c:934
smpboot_thread_fn+0x4b0/0x96c kernel/smpboot.c:164
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
irq event stamp: 1114523
hardirqs last enabled at (1114522): [<ffff8000121b9b0c>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (1114522): [<ffff8000121b9b0c>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (1114523): [<ffff8000121b996c>] __raw_spin_lock_irq include/linux/spinlock_api_smp.h:117 [inline]
hardirqs last disabled at (1114523): [<ffff8000121b996c>] _raw_spin_lock_irq+0x34/0x9c kernel/locking/spinlock.c:170
softirqs last enabled at (1111534): [<ffff800008020d74>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (1111534): [<ffff800008020d74>] __do_softirq+0xc14/0xea0 kernel/softirq.c:600
softirqs last disabled at (1111559): [<ffff8000081c893c>] run_ksoftirqd+0x68/0x258 kernel/softirq.c:934
---[ end trace 0000000000000000 ]---
TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters.
TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters.
TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters.
TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters.


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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.