[v6.1] WARNING in io_ring_exit_work (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 52f863f820fd Linux 6.1.120
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16ccc2df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4fcb3bdeefdffc5
dashboard link: https://syzkaller.appspot.com/bug?extid=83fce5ee5b6c9ab573b6
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/0b5925d752d3/disk-52f863f8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3ce049167860/vmlinux-52f863f8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e8baa2576794/Image-52f863f8.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 4388 at io_uring/io_uring.c:2798 io_ring_exit_work+0x2c8/0x674
Modules linked in:
CPU: 1 PID: 4388 Comm: kworker/u4:7 Tainted: G W 6.1.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: events_unbound io_ring_exit_work
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : io_ring_exit_work+0x2c8/0x674
lr : io_ring_exit_work+0x2c4/0x674 io_uring/io_uring.c:2798
sp : ffff8000216979c0
x29: ffff800021697b00 x28: 0000000000000000 x27: ffff80001295d6c0
x26: 0000000000001770 x25: 1fffe0001936a64c x24: ffff0000c9b53260
x23: ffff0000c9b53018 x22: dfff800000000000 x21: 1fffe0001936a603
x20: ffff800021697a40 x19: ffffffffffffffee x18: 1fffe000367a0576
x17: ffff800015a7d000 x16: ffff8000084f417c x15: ffff0001b3d02bbc
x14: 1ffff00002b500b2 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800012314b2c
x8 : ffff0000d0ad8000 x7 : ffff80000aacefec x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000123f9a64
x2 : 0000000000000000 x1 : ffffffffffffffee x0 : 0000000000000000
Call trace:
io_ring_exit_work+0x2c8/0x674
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2292
worker_thread+0x8e4/0xfec kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864
irq event stamp: 593934
hardirqs last enabled at (593933): [<ffff80001240aa54>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline]
hardirqs last enabled at (593933): [<ffff80001240aa54>] _raw_spin_unlock_irq+0x3c/0x90 kernel/locking/spinlock.c:202
hardirqs last disabled at (593934): [<ffff8000123247d4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (591598): [<ffff8000081c3418>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (591598): [<ffff8000081c3418>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:599
softirqs last disabled at (591431): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:605
---[ 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

[syzbot]

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