From: Benjamin Coddington <bcodding@redhat.com>
To: Anna Schumaker <Anna.Schumaker@netapp.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Dentry revalidation fixups
Date: Wed, 5 Feb 2020 09:01:51 -0500 [thread overview]
Message-ID: <cover.1580910601.git.bcodding@redhat.com> (raw)
Trond's helped me out with my dentry revalidation woes. The first two
patches fix races that may occur, and the third patch fixes a problem I've
tried to solve in the past where the client can decide not to revalidate a
dentry because we hold a delegation, but really it should be revalidated
because we cached that dentry before the delegation. The most recent
attempt and discussion of that problem was here:
https://lore.kernel.org/linux-nfs/bcb5ffd399c4434730e6d100a5b7cae5e207244e.1580225161.git.bcodding@redhat.com/#t
That patch went to linux-next and should be dropped. Anna, it looks like
you've already dropped it, but I just wanted to make a note of it.
Thanks for all the help, Trond!
Trond Myklebust (3):
NFS: Fix up directory verifier races
NFSv4: Fix races between open and dentry revalidation
NFSv4: Fix revalidation of dentries with delegations
fs/nfs/delegation.c | 6 ++
fs/nfs/dir.c | 124 +++++++++++++++++++++++++++++++++++++----
fs/nfs/inode.c | 1 +
fs/nfs/nfs4file.c | 1 -
fs/nfs/nfs4proc.c | 18 +++++-
include/linux/nfs_fs.h | 26 ++-------
6 files changed, 143 insertions(+), 33 deletions(-)
--
2.20.1
next reply other threads:[~2020-02-05 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 14:01 Benjamin Coddington [this message]
2020-02-05 14:01 ` [PATCH 1/3] NFS: Fix up directory verifier races Benjamin Coddington
2020-02-05 14:01 ` [PATCH 2/3] NFSv4: Fix races between open and dentry revalidation Benjamin Coddington
2020-02-05 14:01 ` [PATCH 3/3] NFSv4: Fix revalidation of dentries with delegations Benjamin Coddington
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=cover.1580910601.git.bcodding@redhat.com \
--to=bcodding@redhat.com \
--cc=Anna.Schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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 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.