From: Christoph Hellwig <hch@lst.de>
To: stummala@codeaurora.org
Cc: Junxiao Bi <junxiao.bi@oracle.com>,
Joel Becker <jlbec@evilplan.org>, Christoph Hellwig <hch@lst.de>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] configfs: Fix use-after-free when accessing sd->s_dentry
Date: Fri, 17 May 2019 10:23:12 +0200 [thread overview]
Message-ID: <20190517082312.GA13457@lst.de> (raw)
In-Reply-To: <0081e5c8083f5ed9f1c1e9b456739728@codeaurora.org>
On Thu, May 16, 2019 at 06:27:53PM +0530, stummala@codeaurora.org wrote:
> Hi Christoph, Al,
>
> Can you please consider this patch for merging?
I've been sitting on this for a while, mostly because I can't convince
myself it is safe. What protects other threads from using ->s_dentry
just when we clear it? Also why would sd->s_dentry == dentry ever be
false?
next prev parent reply other threads:[~2019-05-17 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 11:18 [PATCH v2] configfs: Fix use-after-free when accessing sd->s_dentry Sahitya Tummala
2019-01-31 3:20 ` Sahitya Tummala
2019-05-16 12:57 ` stummala
2019-05-17 8:23 ` Christoph Hellwig [this message]
2019-05-23 3:49 ` Sahitya Tummala
2019-05-28 6:11 ` Christoph Hellwig
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=20190517082312.GA13457@lst.de \
--to=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=junxiao.bi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stummala@codeaurora.org \
--cc=viro@zeniv.linux.org.uk \
/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.