linux-kernel - Re: [syzbot] Monthly io-uring report (Jun 2024)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <dc126f39-e5a1-4ebe-98ed-ec615f553bb4@kernel.dk>
Date: Fri, 28 Jun 2024 14:41:00 -0600
From: Jens Axboe <axboe@...nel.dk>
To: syzbot <syzbot+list9762eac493f50a993bbb@...kaller.appspotmail.com>,
 io-uring@...r.kernel.org, linux-kernel@...r.kernel.org,
 syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] Monthly io-uring report (Jun 2024)

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