From: Nix <nix@esperi.org.uk>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org, Neil Brown <neilb@suse.de>
Subject: Re: [PATCH 1/3] NFS: Don't invalidate a submounted dentry in nfs_prime_dcache()
Date: Thu, 12 Mar 2015 23:15:10 +0000 [thread overview]
Message-ID: <87wq2llse9.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <1424736897-95767-1-git-send-email-trond.myklebust@primarydata.com> (Trond Myklebust's message of "Mon, 23 Feb 2015 19:14:55 -0500")
On 24 Feb 2015, Trond Myklebust stated:
> If we're traversing a directory which contains a submounted filesystem,
> or one that has a referral, the NFS server that is processing the READDIR
> request will often return information for the underlying (mounted-on)
> directory. It may, or may not, also return filehandle information.
FWIW, this never seems to have made it into 3.19.x, nor is it in the
stable queue. Was this intentional?
> Cc: stable@vger.kernel.org # 3.18+
(... hm, I guess so...)
--
NULL && (void)
prev parent reply other threads:[~2015-03-12 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 0:14 [PATCH 1/3] NFS: Don't invalidate a submounted dentry in nfs_prime_dcache() Trond Myklebust
2015-02-24 0:14 ` [PATCH 2/3] NFSv3: Use the readdir fileid as the mounted-on-fileid Trond Myklebust
2015-02-24 0:14 ` [PATCH 3/3] NFS: Don't require a filehandle to refresh the inode in nfs_prime_dcache() Trond Myklebust
2015-02-24 21:53 ` NeilBrown
2015-02-24 21:46 ` [PATCH 2/3] NFSv3: Use the readdir fileid as the mounted-on-fileid NeilBrown
2015-02-24 3:09 ` [PATCH 1/3] NFS: Don't invalidate a submounted dentry in nfs_prime_dcache() Trond Myklebust
2015-02-24 21:49 ` NeilBrown
2015-02-25 0:17 ` Trond Myklebust
2015-02-24 21:44 ` NeilBrown
2015-03-12 23:15 ` Nix [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=87wq2llse9.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=trond.myklebust@primarydata.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