[v5.15] WARNING in io_ring_exit_work (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b9d57c40a767 Linux 5.15.203
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17ca0836580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=f35b0882976c49320f71
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/34313629ba4f/disk-b9d57c40.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/402f526e5a98/vmlinux-b9d57c40.xz
kernel image: https://storage.googleapis.com/syzbot-assets/45f7694e9617/bzImage-b9d57c40.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4448 at io_uring/io_uring.c:9553 io_ring_exit_work+0x331/0x1200 io_uring/io_uring.c:9553
Modules linked in:
CPU: 0 PID: 4448 Comm: kworker/u4:8 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x331/0x1200 io_uring/io_uring.c:9553
Code: 78 23 e8 82 73 99 fd 48 8b 7c 24 28 48 8b 74 24 20 e8 33 7d e5 05 48 85 c0 75 29 e8 69 73 99 fd e9 08 fe ff ff e8 5f 73 99 fd <0f> 0b b8 70 17 00 00 48 89 44 24 20 eb cf e8 4c 73 99 fd 0f 0b e9
RSP: 0018:ffffc900012ffaa0 EFLAGS: 00010293
RAX: ffffffff83dfc131 RBX: ffff8880245124a0 RCX: ffff88807dc8d940
RDX: 0000000000000000 RSI: fffffffffffffffb RDI: 0000000000000000
RBP: ffffc900012ffc30 R08: ffff888024512603 R09: 1ffff110048a24c0
R10: dffffc0000000000 R11: ffffed10048a24c1 R12: 000000010000a7ad
R13: dffffc0000000000 R14: 000000010000a7b2 R15: 1ffff110048a2494
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcd90f1eeb8 CR3: 00000000201ca000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work+0x85f/0x1010 kernel/workqueue.c:2310
worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>


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