From: NeilBrown <neilb@suse.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org, Jeff Layton <jlayton@redhat.com>
Subject: [PATCH 0/2] Resolve d_weak_revalidate issues in NFS
Date: Fri, 25 Aug 2017 17:34:41 +1000 [thread overview]
Message-ID: <150364635600.31291.11905399689488751395.stgit@noble> (raw)
Following my recent investigations into d_weak_revalidate
I offer these two patches. The first fixes two closely
related bugs caused by the introduction of d_weak_revalidate.
The second provides a minor code cleanup.
It seems we really do need d_weak_revalidate, but we might
need better documentation describing its purpose.
Thanks,
NeilBrown
---
NeilBrown (2):
NFS: revalidate "." etc correctly on "open".
NFS: remove special-case revalidate in nfs_opendir()
fs/nfs/dir.c | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
--
Signature
next reply other threads:[~2017-08-25 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 7:34 NeilBrown [this message]
2017-08-25 7:34 ` [PATCH 1/2] NFS: revalidate "." etc correctly on "open" NeilBrown
2017-08-25 7:34 ` [PATCH 2/2] NFS: remove special-case revalidate in nfs_opendir() NeilBrown
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=150364635600.31291.11905399689488751395.stgit@noble \
--to=neilb@suse.com \
--cc=anna.schumaker@netapp.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--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