From: Jens Axboe <[email protected]>
To: syzbot
<[email protected]>,
[email protected], [email protected],
[email protected]
Subject: Re: [syzbot] Monthly io-uring report
Date: Mon, 27 Mar 2023 12:23:24 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/27/23 5:01?AM, syzbot wrote:
> 1873 Yes WARNING in split_huge_page_to_list (2)
> https://syzkaller.appspot.com/bug?extid=07a218429c8d19b1fb25
> 38 Yes KASAN: use-after-free Read in nfc_llcp_find_local
> https://syzkaller.appspot.com/bug?extid=e7ac69e6a5d806180b40
These two are not io_uring. Particularly for the latter, I think syzbot
has a tendency to guess it's io_uring if any kind of task_work is
involved. That means anything off fput ends up in that bucket. Can we
get that improved please?
--
Jens Axboe
next prev parent reply other threads:[~2023-03-27 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 11:01 [syzbot] Monthly io-uring report syzbot
2023-03-27 18:23 ` Jens Axboe [this message]
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