From: Dipanjan Das <[email protected]>
To: Dylan Yudaken <[email protected]>
Cc: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: KASAN: use-after-free Read in __io_remove_buffers
Date: Mon, 25 Jul 2022 22:00:30 -0700 [thread overview]
Message-ID: <CANX2M5aYZ2kj+OZHUQF78O_fZoF0Oegytx4iFKjU+mAf9JtQbA@mail.gmail.com> (raw)
In-Reply-To: <CANX2M5YXHVTZfst7h5vkPtyt-xBTn1-zsoA=XUAWztbVurioOA@mail.gmail.com>
> On Thu, Jul 21, 2022 at 4:06 AM Dylan Yudaken <[email protected]> wrote:
> >
> > Both of the bug reports you sent seem to be fixed by the patch I just
> > sent.
> >
> > This one however does not seem to terminate once fixed. Is there an
> > expected run time?
>
We can confirm that the C-repro hangs while the syz-repro does not.
For the unpatched kernel, the repro triggers the bug in less than a
minute.
--
Thanks and Regards,
Dipanjan
next prev parent reply other threads:[~2022-07-26 5:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 1:41 KASAN: use-after-free Read in __io_remove_buffers Dipanjan Das
2022-07-21 11:06 ` Dylan Yudaken
2022-07-24 7:30 ` Dipanjan Das
2022-07-26 5:00 ` Dipanjan Das [this message]
2022-07-26 8:43 ` Dylan Yudaken
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=CANX2M5aYZ2kj+OZHUQF78O_fZoF0Oegytx4iFKjU+mAf9JtQbA@mail.gmail.com \
[email protected] \
[email protected] \
[email protected] \
[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