From: Jens Axboe <[email protected]>
To: syzbot
<[email protected]>,
[email protected], [email protected],
[email protected]
Subject: Re: [syzbot] Monthly io-uring report (Jun 2024)
Date: Fri, 28 Jun 2024 14:41:00 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/28/24 3:41 AM, 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, 3 new issues were detected and 1 were fixed.
> In total, 6 issues are still open and 94 have been fixed so far.
>
> Some of the still happening issues:
>
> Ref Crashes Repro Title
> <1> 3582 Yes general protection fault in try_to_wake_up (2)
> https://syzkaller.appspot.com/bug?extid=b4a81dc8727e513f364d
> <2> 16 Yes KMSAN: uninit-value in io_req_cqe_overflow (3)
> https://syzkaller.appspot.com/bug?extid=e6616d0dc8ded5dc56d6
> <3> 2 No KCSAN: data-race in io_worker_handle_work / io_wq_worker_cancel (3)
> https://syzkaller.appspot.com/bug?extid=90b0e38244e035ec327c
None of these should be valid anymore. 1 is ancient, and all the more
recent testing and reports I see of this are not even related to
io_uring, or the original report.
2 should be fixed Linus's tree, and 3 was fixed for 6.11 as it isn't
really important. But my two attempts at getting a re-run of those had a
failure on the syzbot side.
Please close them, thanks.
--
Jens Axboe
prev parent reply other threads:[~2024-06-28 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 9:41 [syzbot] Monthly io-uring report (Jun 2024) syzbot
2024-06-28 20:41 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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