From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neilb@suse.de>, Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 0/9 v3] support admin-revocation of v4 state
Date: Fri, 17 Nov 2023 07:25:20 -0500 [thread overview]
Message-ID: <9e18d992cdccf56d26482adc8c1c4a6012c68f8e.camel@kernel.org> (raw)
In-Reply-To: <20231117022121.23310-1-neilb@suse.de>
On Fri, 2023-11-17 at 13:18 +1100, NeilBrown wrote:
> This set adds a prequel series to my previous posting which addresses
> some locking problems around ->sc_type and splits that field into
> to separate fields: sc_type and sc_status.
> The recovation code is modified to accomodate these changed.
>
> Thanks
> NeilBrown
>
> [PATCH 1/9] nfsd: hold ->cl_lock for hash_delegation_locked()
> [PATCH 2/9] nfsd: avoid race after unhash_delegation_locked()
> [PATCH 3/9] nfsd: split sc_status out of sc_type
> [PATCH 4/9] nfsd: prepare for supporting admin-revocation of state
> [PATCH 5/9] nfsd: allow admin-revoked state to appear in
> [PATCH 6/9] nfsd: allow admin-revoked NFSv4.0 state to be freed.
> [PATCH 7/9] nfsd: allow lock state ids to be revoked and then freed
> [PATCH 8/9] nfsd: allow open state ids to be revoked and then freed
> [PATCH 9/9] nfsd: allow delegation state ids to be revoked and then
>
Nice set. I like this overall. One (other) question: do we need to add
handling for revoking layout stateids as well?
I'll plan to pull this into my local branch for some testing over the
weekend.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-11-17 12:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 2:18 [PATCH 0/9 v3] support admin-revocation of v4 state NeilBrown
2023-11-17 2:18 ` [PATCH 1/9] nfsd: hold ->cl_lock for hash_delegation_locked() NeilBrown
2023-11-17 10:59 ` Jeff Layton
2023-11-19 21:37 ` NeilBrown
2023-11-19 23:38 ` Chuck Lever
2023-11-19 23:41 ` NeilBrown
2023-11-17 15:04 ` Chuck Lever
2023-11-19 22:07 ` NeilBrown
2023-11-17 2:18 ` [PATCH 2/9] nfsd: avoid race after unhash_delegation_locked() NeilBrown
2023-11-17 11:41 ` Jeff Layton
2023-11-17 19:43 ` Chuck Lever
2023-11-19 22:23 ` NeilBrown
2023-11-19 23:41 ` Chuck Lever
2023-11-17 2:18 ` [PATCH 3/9] nfsd: split sc_status out of sc_type NeilBrown
2023-11-17 19:52 ` Chuck Lever
2023-11-19 22:35 ` NeilBrown
2023-11-17 2:18 ` [PATCH 4/9] nfsd: prepare for supporting admin-revocation of state NeilBrown
2023-11-17 2:18 ` [PATCH 5/9] nfsd: allow admin-revoked state to appear in /proc/fs/nfsd/clients/*/states NeilBrown
2023-11-17 11:27 ` Jeff Layton
2023-11-19 22:36 ` NeilBrown
2023-11-17 2:18 ` [PATCH 6/9] nfsd: allow admin-revoked NFSv4.0 state to be freed NeilBrown
2023-11-17 11:34 ` Jeff Layton
2023-11-19 22:40 ` NeilBrown
2023-11-17 19:58 ` Chuck Lever
2023-11-19 22:47 ` NeilBrown
2023-11-19 23:44 ` Chuck Lever
2023-11-17 2:18 ` [PATCH 7/9] nfsd: allow lock state ids to be revoked and then freed NeilBrown
2023-11-17 2:18 ` [PATCH 8/9] nfsd: allow open " NeilBrown
2023-11-17 2:18 ` [PATCH 9/9] nfsd: allow delegation " NeilBrown
2023-11-17 12:25 ` Jeff Layton [this message]
2023-11-19 23:21 ` [PATCH 0/9 v3] support admin-revocation of v4 state 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=9e18d992cdccf56d26482adc8c1c4a6012c68f8e.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tom@talpey.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