From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+99938118dfd9e1b0741a@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] KASAN: use-after-free Read in bio_poll
Date: Thu, 19 May 2022 13:01:25 +0200 [thread overview]
Message-ID: <CACT4Y+Z9GUz7xK8YKuVewTEopCUWX9tCRhWZq3O84Lw-ZRXd+w@mail.gmail.com> (raw)
In-Reply-To: <0e1b3d10-ae79-f987-187e-58109441ccee@kernel.dk>
On Tue, 10 May 2022 at 14:45, Jens Axboe <axboe@kernel.dk> wrote:
>
> On 5/9/22 11:50 PM, Christoph Hellwig wrote:
> > On Tue, May 10, 2022 at 08:13:58AM +0800, Ming Lei wrote:
> >>> Guys, should we just queue:
> >>>
> >>> ommit 9650b453a3d4b1b8ed4ea8bcb9b40109608d1faf
> >>> Author: Ming Lei <ming.lei@redhat.com>
> >>> Date: Wed Apr 20 22:31:10 2022 +0800
> >>>
> >>> block: ignore RWF_HIPRI hint for sync dio
> >>>
> >>> up for 5.18 and stable?
> >>
> >> I am fine with merging to 5.18 & stable.
> >
> > I'm fine, too. But are we sure this actually is one and the same
> > issue? Otherwise I'll try to find some time to feed it to syzbot
> > first.
>
> I re-wrote the reproducer a bit and can reproduce it, so I can certainly
> test a backport. But yes, I was skeptical on this being the same issue
> too. My initial reaction was that this is likely due to the bio being
> "downgraded" from polled to IRQ driven, and hence completes without an
> extra reference before the bio_poll() is done on it. Which is not the
> issue described in the referenced commit.
#syz fix: block: ignore RWF_HIPRI hint for sync dio
next prev parent reply other threads:[~2022-05-19 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 16:14 [syzbot] KASAN: use-after-free Read in bio_poll syzbot
2022-05-09 17:02 ` Jens Axboe
2022-05-10 0:13 ` Ming Lei
2022-05-10 5:50 ` Christoph Hellwig
2022-05-10 12:45 ` Jens Axboe
2022-05-19 11:01 ` Dmitry Vyukov [this message]
2022-05-09 21:50 ` syzbot
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=CACT4Y+Z9GUz7xK8YKuVewTEopCUWX9tCRhWZq3O84Lw-ZRXd+w@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+99938118dfd9e1b0741a@syzkaller.appspotmail.com \
--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.