From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: <linux-nfs@vger.kernel.org>,
lilingfeng3@huawei.com, yangerkun@huawei.com,
yi.zhang@huawei.com, houtao1@huawei.com, chengzhihao1@huawei.com,
yukuai3@huawei.com, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v3 0/2] provide locking for v4_end_grace
Date: Sat, 13 Dec 2025 13:41:58 -0500 [thread overview]
Message-ID: <20251213184200.585652-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
Following up on:
https://lore.kernel.org/linux-nfs/175136659151.565058.6474755472267609432@noble.neil.brown.name/#r
This is now two patches: one that can be backported, and one that
simplifies the fix based on mechanisms available only in recent
kernels. I've also addressed all the review comments I could find.
These patches have been compile-tested only.
NeilBrown (2):
nfsd: provide locking for v4_end_grace
nfsd: use workqueue enable/disable APIs for v4_end_grace sync
fs/nfsd/netns.h | 1 +
fs/nfsd/nfs4state.c | 40 +++++++++++++++++++++++++++++++++++++---
fs/nfsd/nfsctl.c | 3 +--
fs/nfsd/state.h | 2 +-
4 files changed, 40 insertions(+), 6 deletions(-)
--
2.52.0
next reply other threads:[~2025-12-13 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 18:41 Chuck Lever [this message]
2025-12-13 18:41 ` [PATCH v3 1/2] nfsd: provide locking for v4_end_grace Chuck Lever
2025-12-14 1:05 ` Jeff Layton
2025-12-15 7:28 ` Li Lingfeng
2025-12-13 18:42 ` [PATCH v3 2/2] nfsd: use workqueue enable/disable APIs for v4_end_grace sync Chuck Lever
2025-12-14 1:07 ` Jeff Layton
2025-12-15 8:00 ` Li Lingfeng
2025-12-14 1:08 ` [PATCH v3 0/2] provide locking for v4_end_grace 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=20251213184200.585652-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=houtao1@huawei.com \
--cc=jlayton@kernel.org \
--cc=lilingfeng3@huawei.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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).