From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.15 .. and continuation of merge window
Date: Thu, 12 Jun 2014 02:56:05 +0900 [thread overview]
Message-ID: <26330.1402509365@jrobl> (raw)
In-Reply-To: <20140611123022.GW18016@ZenIV.linux.org.uk>
Al Viro:
> The former guarantees that the address we are doing trylock on would be that
> of a live dentry. The latter makes sure that anything assigned to
> dentry->d_parent after we drop ->d_lock will not be freed until we drop
> rcu_read_lock.
Although I don't know how to reproduce the problem for the latter case,
I think the patch is good.
J. R. Okajima
prev parent reply other threads:[~2014-06-11 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 18:52 Linux 3.15 .. and continuation of merge window Linus Torvalds
2014-06-09 3:30 ` J. R. Okajima
2014-06-11 1:10 ` Al Viro
2014-06-11 9:32 ` J. R. Okajima
2014-06-11 12:30 ` Al Viro
2014-06-11 17:56 ` J. R. Okajima [this message]
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=26330.1402509365@jrobl \
--to=hooanon05g@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox