* [syzbot] Monthly io-uring report (Jun 2024)
@ 2024-06-28 9:41 syzbot
2024-06-28 20:41 ` Jens Axboe
0 siblings, 1 reply; 2+ messages in thread
From: syzbot @ 2024-06-28 9:41 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, 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
---
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 [email protected].
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] 2+ messages in thread
* Re: [syzbot] Monthly io-uring report (Jun 2024)
2024-06-28 9:41 [syzbot] Monthly io-uring report (Jun 2024) syzbot
@ 2024-06-28 20:41 ` Jens Axboe
0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2024-06-28 20:41 UTC (permalink / raw)
To: syzbot, io-uring, linux-kernel, syzkaller-bugs
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-06-28 20:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-06-28 9:41 [syzbot] Monthly io-uring report (Jun 2024) syzbot
2024-06-28 20:41 ` Jens Axboe
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox