From: Trond Myklebust <trondmy@hammerspace.com>
To: "anna@kernel.org" <anna@kernel.org>,
"bcodding@redhat.com" <bcodding@redhat.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2] NFSv4: fairly test all delegations on a SEQ4_ revocation
Date: Mon, 18 Sep 2023 21:58:15 +0000 [thread overview]
Message-ID: <6552638dc081922ca5108fdd3f8cadd1cde6924c.camel@hammerspace.com> (raw)
In-Reply-To: <B39D8F7D-B852-42C9-BC1E-2DED2AC23ACA@redhat.com>
On Mon, 2023-09-18 at 16:36 -0400, Benjamin Coddington wrote:
> On 14 Sep 2023, at 9:18, Benjamin Coddington wrote:
>
> > On 24 Aug 2023, at 14:52, Benjamin Coddington wrote:
> >
> > > When the client is required to use TEST_STATEID to discover which
> > > delegation(s) have been revoked, it may continually test
> > > delegations at the
> > > head of the list if the server continues to be unsatisfied and
> > > send
> > > SEQ4_STATUS_RECALLABLE_STATE_REVOKED. For a large number of
> > > delegations
> > > this behavior is prone to live-lock because the client may never
> > > be able to
> > > test and free revoked state at the end of the list since the
> > > SEQ4_STATUS_RECALLABLE_STATE_REVOKED will cause us to flag
> > > delegations at
> > > the head of the list to be tested. This problem is further
> > > exacerbated by
> > > the state manager's willingness to be scheduled out on a busy
> > > system while
> > > testing the list of delegations.
> > >
> > > Keep a generation counter for each attempt to test all
> > > delegations, and
> > > skip delegations that have already been tested in the current
> > > pass.
> > >
> > > Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
> >
> > This one went through the ringer in an environment that saw
> > multiple clients
> > live-locking, and resolves the problem for them. They asked me to
> > add:
> >
> > Tested-by: Torkil Svensgaard <torkil@drcmr.dk>
> > Tested-by: Ruben Vestergaard <rubenv@drcmr.dk>
> >
> > Ben
>
> Did this one get rejected with a reason? This fix could also be
> implemented
> with flag (as I mentioned in a reply on v2).
>
> Ben
>
Speaking only for myself, I haven't yet had time to properly review it.
So not yet rejected by me.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
prev parent reply other threads:[~2023-09-18 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 18:42 [PATCH] NFSv4: fairly test all delegations on a SEQ4_ revocation Benjamin Coddington
2023-08-24 18:52 ` [PATCH v2] " Benjamin Coddington
2023-08-25 10:55 ` Benjamin Coddington
2023-09-14 13:18 ` Benjamin Coddington
2023-09-18 20:36 ` Benjamin Coddington
2023-09-18 21:58 ` Trond Myklebust [this message]
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=6552638dc081922ca5108fdd3f8cadd1cde6924c.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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).