From: pragalla@codeaurora.org
To: John Garry <john.garry@huawei.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
axboe@kernel.dk, evgreen@google.com, jianchao.w.wang@oracle.com,
linux-block@vger.kernel.org, stummala@codeaurora.org,
Ming Lei <ming.lei@redhat.com>
Subject: Re: use-after-free access in bt_iter()
Date: Fri, 05 Feb 2021 21:00:04 +0530 [thread overview]
Message-ID: <bbed52ea0c788b07ca68142bd86a07df@codeaurora.org> (raw)
In-Reply-To: <f1027dc3-d5a7-02c8-ef02-e34aeb12c0ac@huawei.com>
On 2021-02-04 21:47, 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.
>
Hi John,
> @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/
>
Yes, i don't have a reliable re-creator. The oops was noticed as a part
of stability testing and
was not an intentional try. This was noticed couple of times.
Please share the steps (if any) to easy hit or to exercise this path
more frequently.
Meanwhile, i will go with the usual stability procedure. i will update
the results here later.
> This should fix the common issue. But no final solution to issues
> discussed from patch 2/2, which is more exotic.
>
> BTW, is this the same Pradeep who reported:
> https://lore.kernel.org/linux-block/1606402925-24420-1-git-send-email-ppvk@codeaurora.org/
>
> I did cc ppvk@codeaurora.org on earlier version of my series, but it
> bounced.
>
Yes, it's the same Pradeep. Unfortunately my old email
"ppvk@codeaurora.org" got expired and
couldn't able to restore. Hence the bounced emails. Now this got
resolved with a new email
"pragalla@codeaurora.org" which I'm now currently replying.
>>
>> See also
>> https://lore.kernel.org/linux-block/1bcc1d9e-6a32-1e00-0d32-f5b7325b2f8c@huawei.com/
>
> Thanks,
> John
Thanks and Regards,
Pradeep
next prev parent reply other threads:[~2021-02-05 19:51 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
2021-02-05 15:30 ` pragalla [this message]
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=bbed52ea0c788b07ca68142bd86a07df@codeaurora.org \
--to=pragalla@codeaurora.org \
--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=ming.lei@redhat.com \
--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