From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jeff Layton <jlayton@redhat.com>
Cc: NeilBrown <neilb@suse.de>,
trond.myklebust@netapp.com, linux-nfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v1] vfs: kill FS_REVAL_DOT by adding a d_reval_jumped dentry op
Date: Thu, 21 Feb 2013 21:51:14 +0000 [thread overview]
Message-ID: <20130221215114.GL4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130221111738.7592bec4@tlielax.poochiereds.net>
On Thu, Feb 21, 2013 at 11:17:38AM -0500, Jeff Layton wrote:
> Also, since this is the last component of the path, I suspect that
> we're almost never going to be in rcu-walk mode here, right?
Take a look at complete_walk(); it starts with leaving RCU mode. Before
it gets anywhere near that call.
next prev parent reply other threads:[~2013-02-21 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 16:19 [PATCH v1] vfs: kill FS_REVAL_DOT by adding a d_reval_jumped dentry op Jeff Layton
2013-02-20 22:32 ` NeilBrown
2013-02-21 16:17 ` Jeff Layton
2013-02-21 21:51 ` Al Viro [this message]
2013-02-22 12:28 ` Jeff Layton
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=20130221215114.GL4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=trond.myklebust@netapp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).