[v6.6] WARNING in io_ring_exit_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c2603c511feb Linux 6.6.93
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1139b50c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link: https://syzkaller.appspot.com/bug?extid=19827bd6deb9b24f655f
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8754f950a6e7/disk-c2603c51.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b19332dbf63/vmlinux-c2603c51.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb245e836038/bzImage-c2603c51.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 48 at io_uring/io_uring.c:3221 io_ring_exit_work+0x39e/0x7e0 io_uring/io_uring.c:3221
Modules linked in:
CPU: 1 PID: 48 Comm: kworker/u4:3 Not tainted 6.6.93-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: iou_exit io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x39e/0x7e0 io_uring/io_uring.c:3221
Code: e8 17 e0 27 f7 48 89 df 48 c7 c6 e0 a9 5d 8a 4c 8b 24 24 4c 89 e2 b9 01 00 00 00 e8 7c aa bd f9 e9 64 ff ff ff e8 f2 df 27 f7 <0f> 0b b8 70 17 00 00 48 89 44 24 08 eb a6 89 d9 80 e1 07 80 c1 03
RSP: 0018:ffffc90000b8fa40 EFLAGS: 00010293
RAX: ffffffff8a5db6ee RBX: 000000010000f990 RCX: ffff88801d27da00
RDX: 0000000000000000 RSI: fffffffffffffffb RDI: 0000000000000000
RBP: ffffc90000b8fbb0 R08: ffffc90000b8f9c7 R09: 1ffff92000171f38
R10: dffffc0000000000 R11: fffff52000171f39 R12: 000000010000f98b
R13: ffff88807bbae288 R14: ffff88807bbae510 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f779fbde000 CR3: 000000005fed3000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000004144
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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