From: syzbot <syzbot+listc8beb21580bd24573228@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 (Apr 2023)
Date: Thu, 27 Apr 2023 10:19:50 -0700 [thread overview]
Message-ID: <0000000000006ac1fb05fa54903e@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, 0 new issues were detected and 0 were fixed.
In total, 18 issues are still open and 88 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3549 Yes WARNING in io_ring_exit_work
https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
<2> 3291 Yes general protection fault in try_to_wake_up (2)
https://syzkaller.appspot.com/bug?extid=b4a81dc8727e513f364d
<3> 783 Yes INFO: task hung in io_ring_exit_work
https://syzkaller.appspot.com/bug?extid=93f72b3885406bb09e0d
<4> 582 Yes KMSAN: uninit-value in io_req_cqe_overflow
https://syzkaller.appspot.com/bug?extid=12dde80bf174ac8ae285
<5> 75 Yes INFO: task hung in io_wq_put_and_exit (3)
https://syzkaller.appspot.com/bug?extid=adb05ed2853417be49ce
---
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:[~2023-04-27 17:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0000000000006ac1fb05fa54903e@google.com \
--to=syzbot+listc8beb21580bd24573228@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.