[v6.1] WARNING in io_ring_exit_work (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 090666d3cc90 Linux 6.1.177
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=167e2ab9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5aae664b2df43c2
dashboard link: https://syzkaller.appspot.com/bug?extid=f2520424bcf7f3a801a5
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0b218516a5e9/disk-090666d3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3239ad568bdf/vmlinux-090666d3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8b19cfbec3e/bzImage-090666d3.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 15425 at io_uring/io_uring.c:2892 io_ring_exit_work+0x329/0x760 io_uring/io_uring.c:2892
Modules linked in:
CPU: 1 PID: 15425 Comm: kworker/u4:12 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/2026
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x329/0x760 io_uring/io_uring.c:2892
Code: 89 fd 48 8b 7c 24 30 48 8b 74 24 08 e8 6e 30 11 00 48 85 c0 75 40 e8 04 40 5a f7 4c 8b 7c 24 10 e9 1e fe ff ff e8 f5 3f 5a f7 <0f> 0b b8 70 17 00 00 48 89 44 24 08 eb c7 44 89 e9 80 e1 07 80 c1
RSP: 0018:ffffc900046e7ac0 EFLAGS: 00010293
RAX: ffffffff8a27e1ab RBX: 1ffff1100e682a03 RCX: ffff88801af81e00
RDX: 0000000000000000 RSI: fffffffffffffffd RDI: 0000000000000000
RBP: ffffc900046e7c30 R08: ffffc900046e7a47 R09: 1ffff920008dcf48
R10: dffffc0000000000 R11: fffff520008dcf49 R12: dffffc0000000000
R13: 000000010002a0bc R14: 000000010002a0bf R15: ffff888073415018
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561095467168 CR3: 000000000c88e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292
worker_thread+0xaf5/0x12a0 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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