public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+list2f3a8c0dbf1ef5c21483@syzkaller.appspotmail.com>
To: axboe@kernel.dk, io-uring@vger.kernel.org,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly io-uring report (Dec 2025)
Date: Thu, 04 Dec 2025 15:05:32 -0800	[thread overview]
Message-ID: <693213bc.a70a0220.2ea503.00ea.GAE@google.com> (raw)

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, 1 new issues were detected and 1 were fixed.
In total, 3 issues are still open and 128 have already been fixed.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 4212    No    WARNING in io_ring_exit_work (2)
                  https://syzkaller.appspot.com/bug?extid=557a278955ff3a4d3938
<2> 46      Yes   INFO: task hung in io_wq_put_and_exit (6)
                  https://syzkaller.appspot.com/bug?extid=4eb282331cab6d5b6588
<3> 1       No    KASAN: slab-use-after-free Read in io_poll_remove_entries (2)
                  https://syzkaller.appspot.com/bug?extid=721cddf316143353975e

---
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.

             reply	other threads:[~2025-12-04 23:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 23:05 syzbot [this message]
2025-12-05  4:05 ` [syzbot] Monthly io-uring report (Dec 2025) Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=693213bc.a70a0220.2ea503.00ea.GAE@google.com \
    --to=syzbot+list2f3a8c0dbf1ef5c21483@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox