From: Ming Lei <ming.lei@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
pragalla@codeaurora.org, axboe@kernel.dk, evgreen@google.com,
jianchao.w.wang@oracle.com, linux-block@vger.kernel.org,
stummala@codeaurora.org
Subject: Re: use-after-free access in bt_iter()
Date: Fri, 5 Feb 2021 10:39:06 +0800 [thread overview]
Message-ID: <20210205023906.GB1498829@T590> (raw)
In-Reply-To: <f1027dc3-d5a7-02c8-ef02-e34aeb12c0ac@huawei.com>
On Thu, Feb 04, 2021 at 04:17:51PM +0000, John Garry wrote:
> On 04/02/2021 15:51, Bart Van Assche wrote:
> > On 2/4/21 3:46 AM,pragalla@codeaurora.org wrote:
> > > Is this issue got fixed on any latest kernel ? if so, can you please
> > > help point the patch ?
> > > If not got fixed, can we have a final solution ? i can even help in
> > > testing the solution.
> > Hi John,
> >
>
> Hi Bart,
>
> > Some time ago you replied the following to an email from me with a
> > suggestion for a fix: "Please let me consider it a bit more." Are you
> > still working on a fix?
>
> Unfortunately I have not had a chance, sorry. But I can look again.
>
> So I have only seen KASAN use-after-free's myself, but never an actual oops.
> IIRC, someone did report an oops.
>
> @Pradeep, do you have a reliable re-creator? I noticed the timeout handler
> stackframe in your mail, so I guess not. However, as an experiment, could
> you test:
> https://lore.kernel.org/linux-block/1608203273-170555-2-git-send-email-john.garry@huawei.com/
>
> This should fix the common issue. But no final solution to issues discussed
> from patch 2/2, which is more exotic.
>
If still no progress, I'd suggest to consider the patches I posted:
https://lore.kernel.org/linux-block/accb98d8-8186-2e74-a5c3-e0f09ce2b3ff@acm.org/#r
The idea is quite simple at least, :-)
--
Ming
next prev parent reply other threads:[~2021-02-05 2:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 11:46 use-after-free access in bt_iter() pragalla
2021-02-04 15:51 ` Bart Van Assche
2021-02-04 16:17 ` John Garry
2021-02-05 2:39 ` Ming Lei [this message]
2021-02-05 15:30 ` pragalla
2021-02-05 16:07 ` John Garry
[not found] ` <9ace4c26c47e84c3c6a1c68ef1a193f8@codeaurora.org>
2021-02-19 6:22 ` pragalla
2021-02-19 9:34 ` John Garry
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=20210205023906.GB1498829@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=evgreen@google.com \
--cc=jianchao.w.wang@oracle.com \
--cc=john.garry@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=pragalla@codeaurora.org \
--cc=stummala@codeaurora.org \
/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