syzbot


WARNING in io_ring_exit_work (2)

Status: upstream: reported on 2024/02/22 09:35
Subsystems: io-uring
[Documentation on labels]
Reported-by: syzbot+557a278955ff3a4d3938@syzkaller.appspotmail.com
First crash: 63d, last: 6d17h
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly io-uring report (Apr 2024) 0 (1) 2024/04/15 09:23
[syzbot] [io-uring?] WARNING in io_ring_exit_work (2) 0 (1) 2024/02/22 09:35
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 WARNING in io_ring_exit_work 5 284d 375d 0/3 auto-obsoleted due to no activity on 2023/10/19 11:52
linux-5.15 WARNING in io_ring_exit_work 9 277d 384d 0/3 auto-obsoleted due to no activity on 2023/10/27 08:42
upstream WARNING in io_ring_exit_work io-uring C done done 3550 358d 1132d 0/26 auto-obsoleted due to no activity on 2023/07/28 02:36

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 50 at io_uring/io_uring.c:3075 io_ring_exit_work+0x39b/0x850 io_uring/io_uring.c:3075
Modules linked in:
CPU: 0 PID: 50 Comm: kworker/u8:3 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x39b/0x850 io_uring/io_uring.c:3075
Code: 23 e8 69 0a 22 f6 48 8b 7c 24 10 48 8b 74 24 08 e8 ca b9 0a 00 48 85 c0 75 3d e8 50 0a 22 f6 e9 96 fd ff ff e8 46 0a 22 f6 90 <0f> 0b 90 b8 70 17 00 00 48 89 44 24 08 eb cd 44 89 f9 80 e1 07 80
RSP: 0018:ffffc90000ba7a40 EFLAGS: 00010293
RAX: ffffffff8b72eb0a RBX: 00000001000044d0 RCX: ffff888014da9e00
RDX: 0000000000000000 RSI: fffffffffffffffe RDI: 0000000000000000
RBP: ffffc90000ba7bb0 R08: ffffffff8b72eadd R09: 1ffff92000174f38
R10: dffffc0000000000 R11: fffff52000174f39 R12: 00000001000044ce
R13: ffff888056890288 R14: ffff888056890538 R15: ffff888056890000
FS:  0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbb9afff000 CR3: 00000000742f4000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 process_one_work kernel/workqueue.c:3254 [inline]
 process_scheduled_works+0xa02/0x1770 kernel/workqueue.c:3335
 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416
 kthread+0x2f2/0x390 kernel/kthread.c:388
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/14 15:56 upstream fe46a7dd189e c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING in io_ring_exit_work
2024/02/18 09:25 linux-next 2c3b09aac00d 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root WARNING in io_ring_exit_work
* Struck through repros no longer work on HEAD.