From: syzbot <[email protected]>
To: [email protected], [email protected],
[email protected], [email protected]
Subject: [syzbot] Monthly io-uring report
Date: Mon, 27 Mar 2023 04:01:54 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hello io-uring maintainers/developers,
This is a 30-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, 5 new issues were detected and 0 were fixed.
In total, 49 issues are still open and 105 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
3393 Yes WARNING in io_ring_exit_work
https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
3241 Yes general protection fault in try_to_wake_up (2)
https://syzkaller.appspot.com/bug?extid=b4a81dc8727e513f364d
1873 Yes WARNING in split_huge_page_to_list (2)
https://syzkaller.appspot.com/bug?extid=07a218429c8d19b1fb25
772 Yes INFO: task hung in io_ring_exit_work
https://syzkaller.appspot.com/bug?extid=93f72b3885406bb09e0d
718 Yes KASAN: use-after-free Read in io_poll_remove_entries
https://syzkaller.appspot.com/bug?extid=cd301bb6523ea8cc8ca2
443 Yes KMSAN: uninit-value in io_req_cqe_overflow
https://syzkaller.appspot.com/bug?extid=12dde80bf174ac8ae285
73 Yes INFO: task hung in io_wq_put_and_exit (3)
https://syzkaller.appspot.com/bug?extid=adb05ed2853417be49ce
38 Yes KASAN: use-after-free Read in nfc_llcp_find_local
https://syzkaller.appspot.com/bug?extid=e7ac69e6a5d806180b40
---
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].
next reply other threads:[~2023-03-27 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 11:01 syzbot [this message]
2023-03-27 18:23 ` [syzbot] Monthly io-uring report Jens Axboe
2023-03-27 19:12 ` Aleksandr Nogikh
2023-03-27 19:20 ` Jens Axboe
2023-03-27 20:12 ` Aleksandr Nogikh
2023-03-27 19:21 ` Eric Biggers
2023-03-27 19:25 ` Jens Axboe
2023-03-27 19:56 ` Eric Biggers
2023-03-27 20:00 ` Jens Axboe
2023-03-27 20:21 ` Aleksandr Nogikh
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