* [syzbot] Monthly io-uring report (Jan 2026)
@ 2026-01-14 6:52 syzbot
0 siblings, 0 replies; only message in thread
From: syzbot @ 2026-01-14 6:52 UTC (permalink / raw)
To: axboe, io-uring, linux-kernel, syzkaller-bugs
Hello io-uring maintainers/developers,
This is a 31-day syzbot report for the io-uring subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/io-uring
During the period, 0 new issues were detected and 1 were fixed.
In total, 3 issues are still open and 133 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 5002 No WARNING in io_ring_exit_work (2)
https://syzkaller.appspot.com/bug?extid=557a278955ff3a4d3938
<2> 68 Yes INFO: task hung in io_wq_put_and_exit (6)
https://syzkaller.appspot.com/bug?extid=4eb282331cab6d5b6588
<3> 30 No INFO: rcu detected stall in io_ring_exit_work (3)
https://syzkaller.appspot.com/bug?extid=33504742c13bcd6c9541
---
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 syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-01-14 6:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-14 6:52 [syzbot] Monthly io-uring report (Jan 2026) syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox