From: Chuck Lever <chuck.lever@oracle.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: NeilBrown <neilb@suse.de>,
linux-nfs@vger.kernel.org, Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 2/9] nfsd: avoid race after unhash_delegation_locked()
Date: Fri, 17 Nov 2023 14:43:09 -0500 [thread overview]
Message-ID: <ZVfCTVTmNd0cgqcY@tissot.1015granger.net> (raw)
In-Reply-To: <40e3c09538c58818e5ab0c713a49d62304c4c4a0.camel@kernel.org>
On Fri, Nov 17, 2023 at 06:41:37AM -0500, Jeff Layton wrote:
> On Fri, 2023-11-17 at 13:18 +1100, NeilBrown wrote:
> > NFS4_CLOSED_DELEG_STID and NFS4_REVOKED_DELEG_STID are similar in
> > purpose.
> > REVOKED is used for NFSv4.1 states which have been revoked because the
> > lease has expired. CLOSED is used in other cases.
> > The difference has two practical effects.
> > 1/ REVOKED states are on the ->cl_revoked list
> > 2/ REVOKED states result in nfserr_deleg_revoked from
> > nfsd4_verify_open_stid() asnd nfsd4_validate_stateid while
> > CLOSED states result in nfserr_bad_stid.
> >
> > Currently a state that is being revoked is first set to "CLOSED" in
> > unhash_delegation_locked(), then possibly to "REVOKED" in
> > revoke_delegation(), at which point it is added to the cl_revoked list.
> >
> > It is possible that a stateid test could see the CLOSED state
> > which really should be REVOKED, and so return the wrong error code. So
> > it is safest to remove this window of inconsistency.
> >
> > With this patch, unhash_delegation_locked() always set the state
> > correctly, and revoke_delegation() no longer changes the state.
> >
> > Also remove a redundant test on minorversion when
> > NFS4_REVOKED_DELEG_STID is seen - it can only be seen when minorversion
> > is non-zero.
> >
> > Signed-off-by: NeilBrown <neilb@suse.de>
> > ---
> > fs/nfsd/nfs4state.c | 20 ++++++++++----------
> > 1 file changed, 10 insertions(+), 10 deletions(-)
> >
> > diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> > index 6368788a7d4e..7469583382fb 100644
> > --- a/fs/nfsd/nfs4state.c
> > +++ b/fs/nfsd/nfs4state.c
> > @@ -1334,7 +1334,7 @@ static bool delegation_hashed(struct nfs4_delegation *dp)
> > }
> >
> > static bool
> > -unhash_delegation_locked(struct nfs4_delegation *dp)
> > +unhash_delegation_locked(struct nfs4_delegation *dp, unsigned char type)
unsigned short type ?
> > {
> > struct nfs4_file *fp = dp->dl_stid.sc_file;
> >
> > @@ -1343,7 +1343,9 @@ unhash_delegation_locked(struct nfs4_delegation *dp)
> > if (!delegation_hashed(dp))
> > return false;
> >
> > - dp->dl_stid.sc_type = NFS4_CLOSED_DELEG_STID;
> > + if (dp->dl_stid.sc_client->cl_minorversion == 0)
> > + type = NFS4_CLOSED_DELEG_STID;
> > + dp->dl_stid.sc_type = type;
> > /* Ensure that deleg break won't try to requeue it */
> > ++dp->dl_time;
> > spin_lock(&fp->fi_lock);
> > @@ -1359,7 +1361,7 @@ static void destroy_delegation(struct nfs4_delegation *dp)
> > bool unhashed;
> >
> > spin_lock(&state_lock);
> > - unhashed = unhash_delegation_locked(dp);
> > + unhashed = unhash_delegation_locked(dp, NFS4_CLOSED_DELEG_STID);
> > spin_unlock(&state_lock);
> > if (unhashed)
> > destroy_unhashed_deleg(dp);
> > @@ -1373,9 +1375,8 @@ static void revoke_delegation(struct nfs4_delegation *dp)
> >
> > trace_nfsd_stid_revoke(&dp->dl_stid);
> >
> > - if (clp->cl_minorversion) {
> > + if (dp->dl_stid.sc_type == NFS4_REVOKED_DELEG_STID) {
> > spin_lock(&clp->cl_lock);
> > - dp->dl_stid.sc_type = NFS4_REVOKED_DELEG_STID;
> > refcount_inc(&dp->dl_stid.sc_count);
> > list_add(&dp->dl_recall_lru, &clp->cl_revoked);
> > spin_unlock(&clp->cl_lock);
> > @@ -2234,7 +2235,7 @@ __destroy_client(struct nfs4_client *clp)
> > spin_lock(&state_lock);
> > while (!list_empty(&clp->cl_delegations)) {
> > dp = list_entry(clp->cl_delegations.next, struct nfs4_delegation, dl_perclnt);
> > - WARN_ON(!unhash_delegation_locked(dp));
> > + WARN_ON(!unhash_delegation_locked(dp, NFS4_CLOSED_DELEG_STID));
> > list_add(&dp->dl_recall_lru, &reaplist);
> > }
> > spin_unlock(&state_lock);
> > @@ -5197,8 +5198,7 @@ nfs4_check_deleg(struct nfs4_client *cl, struct nfsd4_open *open,
> > goto out;
> > if (deleg->dl_stid.sc_type == NFS4_REVOKED_DELEG_STID) {
> > nfs4_put_stid(&deleg->dl_stid);
> > - if (cl->cl_minorversion)
> > - status = nfserr_deleg_revoked;
> > + status = nfserr_deleg_revoked;
> > goto out;
> > }
> > flags = share_access_to_flags(open->op_share_access);
> > @@ -6235,7 +6235,7 @@ nfs4_laundromat(struct nfsd_net *nn)
> > dp = list_entry (pos, struct nfs4_delegation, dl_recall_lru);
> > if (!state_expired(<, dp->dl_time))
> > break;
> > - WARN_ON(!unhash_delegation_locked(dp));
> > + WARN_ON(!unhash_delegation_locked(dp, NFS4_REVOKED_DELEG_STID));
> > list_add(&dp->dl_recall_lru, &reaplist);
> > }
> > spin_unlock(&state_lock);
> > @@ -8350,7 +8350,7 @@ nfs4_state_shutdown_net(struct net *net)
> > spin_lock(&state_lock);
> > list_for_each_safe(pos, next, &nn->del_recall_lru) {
> > dp = list_entry (pos, struct nfs4_delegation, dl_recall_lru);
> > - WARN_ON(!unhash_delegation_locked(dp));
> > + WARN_ON(!unhash_delegation_locked(dp, NFS4_CLOSED_DELEG_STID));
Neil, what say we get rid of these WARN_ONs?
> > list_add(&dp->dl_recall_lru, &reaplist);
> > }
> > spin_unlock(&state_lock);
>
> Same question here. Should this go to stable? I guess the race is not
> generally fatal...
Again, there's no existing bug report, so no urgency to get this
backported. I would see these changes soak in upstream rather than
pull them into stable quickly only to discover another bug has been
introduced.
We don't have a failing test or a data corruption risk, as far as
I can tell.
> Reviewed-by: Jeff Layton <jlayton@kernel.org>
--
Chuck Lever
next prev parent reply other threads:[~2023-11-17 19:43 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 [this message]
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 ` [PATCH 0/9 v3] support admin-revocation of v4 state Jeff Layton
2023-11-19 23:21 ` 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=ZVfCTVTmNd0cgqcY@tissot.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=Dai.Ngo@oracle.com \
--cc=jlayton@kernel.org \
--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