public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: syzbot
	<syzbot+list2f3a8c0dbf1ef5c21483@syzkaller.appspotmail.com>,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Monthly io-uring report (Dec 2025)
Date: Thu, 4 Dec 2025 21:05:15 -0700	[thread overview]
Message-ID: <9f1d144a-56b8-481a-bfdc-409f3b7e7e3a@kernel.dk> (raw)
In-Reply-To: <693213bc.a70a0220.2ea503.00ea.GAE@google.com>

On 12/4/25 4:05 PM, syzbot wrote:
> 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

FWIW, I think we'll keep hitting variants of this, as syzbot tests with
tons of debugging enabled (for good reason), which slows things down a
_lot_. Then it floods the ring with work, and cancelation/exit can then
take a long time. Whenever I've tested these reproducers, they finish
quite quick. Until you enable all the gunk and run it on a slow CPU or
two. Hence not a real bug imho.

-- 
Jens Axboe

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

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

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=9f1d144a-56b8-481a-bfdc-409f3b7e7e3a@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+list2f3a8c0dbf1ef5c21483@syzkaller.appspotmail.com \
    --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