Re: [syzbot] [io-uring?] WARNING in io_ring_exit_work (2)

syzbot has found a reproducer for the following issue on:

HEAD commit:    4352b8aee980 Merge tag 'i3c/for-7.3' of git://git.kernel.o..
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1369b179580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=335632b21d0ce540
dashboard link: https://syzkaller.appspot.com/bug?extid=557a278955ff3a4d3938
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=139f3549580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8491c9d0d35e/disk-4352b8ae.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/51cc3aee80d1/vmlinux-4352b8ae.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e0bcbebdbede/bzImage-4352b8ae.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
time_after(jiffies, timeout)
WARNING: io_uring/io_uring.c:2356 at io_ring_exit_work+0x4d0/0x9a0 io_uring/io_uring.c:2356, CPU#0: kworker/u8:7/1002
Modules linked in:
CPU: 0 UID: 0 PID: 1002 Comm: kworker/u8:7 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/05/2026
Workqueue: iou_exit io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x4d0/0x9a0 io_uring/io_uring.c:2356
Code: c6 05 c8 2a 38 0f 01 48 c7 c7 80 aa 6a 8c be 25 00 00 00 48 c7 c2 60 a1 6a 8c e8 cb 03 78 00 e9 70 fe ff ff e8 f1 41 9c 00 90 <0f> 0b 90 b8 70 17 00 00 48 89 44 24 38 eb 9a c7 84 24 b0 00 00 00
RSP: 0018:ffffc90004c3f940 EFLAGS: 00010293
RAX: ffffffff812aeb8f RBX: 0000000100003abe RCX: ffff888026cf8000
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000000000000
RBP: ffffc90004c3fad0 R08: ffffc90004c3f8c7 R09: 1ffff92000987f18
R10: dffffc0000000000 R11: fffff52000987f19 R12: dffffc0000000000
R13: 0000000100003abd R14: 0000000000002000 R15: ffff888030d88000
FS:  0000000000000000(0000) GS:ffff888124cf3000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc968890f8 CR3: 0000000082816000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 process_one_work kernel/workqueue.c:3387 [inline]
 process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3470
 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3551
 kthread+0x38b/0x480 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.