[moderation] [io-uring?] WARNING: io_uring/io_uring.c:LINE at io_ring_exit_work, CPU: kworker/u8:NUM/NUM

1 view
Skip to first unread message

syzbot

unread,
Jun 20, 2025, 5:18:36 AM6/20/25
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 050f8ad7b58d Add linux-next specific files for 20250616
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=116e15d4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d2efc7740224b93a
dashboard link: https://syzkaller.appspot.com/bug?extid=de35b7ddbcefcecf6382
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
CC: [ax...@kernel.dk io-u...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/49faa18d2f53/disk-050f8ad7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7c6f9cd7fe5d/vmlinux-050f8ad7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84a08d6403ee/bzImage-050f8ad7.xz

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

------------[ cut here ]------------
WARNING: io_uring/io_uring.c:2946 at io_ring_exit_work+0x4ed/0x930 io_uring/io_uring.c:2946, CPU#1: kworker/u8:10/6034
Modules linked in:
CPU: 1 UID: 0 PID: 6034 Comm: kworker/u8:10 Not tainted 6.16.0-rc2-next-20250616-syzkaller #0 PREEMPT(full)
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+0x4ed/0x930 io_uring/io_uring.c:2946
Code: c6 05 f8 f1 5f 0e 01 48 c7 c7 00 23 e2 8b be 24 00 00 00 48 c7 c2 60 22 e2 8b e8 be 26 73 00 e9 7b fe ff ff e8 14 32 95 00 90 <0f> 0b 90 b8 70 17 00 00 48 89 44 24 38 e9 5f ff ff ff 89 d9 80 e1
RSP: 0018:ffffc9000abdf8e0 EFLAGS: 00010293
RAX: ffffffff812b381c RBX: 000000010000e7c4 RCX: ffff88807faabc00
RDX: 0000000000000000 RSI: fffffffffffffffb RDI: 0000000000000000
RBP: ffffc9000abdfa70 R08: ffffc9000abdf867 R09: 1ffff9200157bf0c
R10: dffffc0000000000 R11: fffff5200157bf0d R12: 000000010000e7bf
R13: ffff8880244e6310 R14: ffff8880244e6480 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff888125d40000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000185030 CR3: 000000007c72a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000097 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work kernel/workqueue.c:3235 [inline]
process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3318
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3399
kthread+0x711/0x8a0 kernel/kthread.c:464
ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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

Aleksandr Nogikh

unread,
Jun 20, 2025, 5:33:37 AM6/20/25
to syzbot, syzkaller-upst...@googlegroups.com
#syz invalid

Dup of "WARNING in io_ring_exit_work" due to a new WARNING format. The
pkg/report code is already fixed, so it should no longer be happening.
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6855276a.a00a0220.137b3.003c.GAE%40google.com.
Reply all
Reply to author
Forward
0 new messages