From: "Benjamin Coddington" <bcodding@redhat.com>
To: "Anna Schumaker" <anna.schumaker@netapp.com>
Cc: "Trond Myklebust" <trond.myklebust@hammerspace.com>,
"Linux NFS Mailing List" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/3] NFSv4: Fix a livelock when CLOSE pre-emptively bumps state sequence
Date: Tue, 22 Sep 2020 10:22:17 -0400 [thread overview]
Message-ID: <8DB79D4D-6986-4114-B031-43157089C2B5@redhat.com> (raw)
In-Reply-To: <CAFX2JfmeOm+-cpq6aTGnBNZLmAOwp8dykTWe7L6OU3mmnSw6rw@mail.gmail.com>
On 22 Sep 2020, at 10:03, Anna Schumaker wrote:
> Hi Ben,
>
> Once I apply this patch I have trouble with generic/478 doing lock reclaim:
>
> [ 937.460505] run fstests generic/478 at 2020-09-22 09:59:14
> [ 937.607990] NFS: __nfs4_reclaim_open_state: Lock reclaim failed!
>
> And the test just hangs until I kill it.
>
> Just thought you should know!
Yes, thanks! I'm not seeing that.. I've tested these based on v5.8.4, I'll
rebase and check again. I see a wirecap of generic/478 is only 515K on my
system, would you be willing to share a capture of your test failing?
Ben
next prev parent reply other threads:[~2020-09-22 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 11:04 [PATCH 1/3] NFSv4: Fix a livelock when CLOSE pre-emptively bumps state sequence Benjamin Coddington
2020-09-21 11:04 ` [PATCH 2/3] NFSv4: Refactor nfs_need_update_open_stateid() Benjamin Coddington
2020-09-21 11:17 ` Benjamin Coddington
2020-09-22 10:14 ` [PATCH 2/3 v2] " Benjamin Coddington
2020-09-21 11:04 ` [PATCH 3/3] NFSv4: cleanup unused zero_stateid copy Benjamin Coddington
2020-09-22 14:03 ` [PATCH 1/3] NFSv4: Fix a livelock when CLOSE pre-emptively bumps state sequence Anna Schumaker
2020-09-22 14:22 ` Benjamin Coddington [this message]
2020-09-22 14:31 ` Anna Schumaker
[not found] ` <CAFX2JfkQSonD=Hnn40Y8A62rfmoQ2d8_ugNvOmg+Ny8zJ6dLAg@mail.gmail.com>
2020-09-22 15:46 ` Benjamin Coddington
2020-09-22 15:53 ` Anna Schumaker
2020-09-22 16:11 ` Anna Schumaker
2020-09-22 18:47 ` Benjamin Coddington
2020-09-22 18:51 ` Anna Schumaker
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=8DB79D4D-6986-4114-B031-43157089C2B5@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 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).