From: "Robert Milkowski" <rmilkowski@gmail.com>
To: "'Chuck Lever'" <chuck.lever@oracle.com>
Cc: "'Linux NFS Mailing List'" <linux-nfs@vger.kernel.org>,
"'Trond Myklebust'" <trondmy@hammerspace.com>,
"'Anna Schumaker'" <Anna.Schumaker@netapp.com>,
"'James Pearson'" <jcpearson@gmail.com>
Subject: RE: NFSv4.0: client stuck looping on RENEW + NFSERR_STALE_CLIENTID
Date: Wed, 10 Jun 2020 17:24:28 +0100 [thread overview]
Message-ID: <119601d63f43$9d55e860$d801b920$@gmail.com> (raw)
In-Reply-To: <7E441550-FCCF-492E-BACB-271A42D4A6C4@oracle.com>
>
> The usual course of action for bugs in distributor kernels is to work
> directly with the distributor. Upstream developers don't generally have
> access to or expertise with those code bases. 7.3 is an older kernel,
> and it's possible that upstream has addressed this issue and CentOS has
> pulled that fix into a newer release.
>
I was hoping someone here might get back with "hey, this has been fixed by
commit...".
We also did see it on centos 7.6
I will try to get it re-produce it and once I can then I'll try to reproduce
it against upstream.
--
Robert Milkowski
next prev parent reply other threads:[~2020-06-10 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 12:34 NFSv4.0: client stuck looping on RENEW + NFSERR_STALE_CLIENTID Robert Milkowski
2020-06-10 16:19 ` Chuck Lever
2020-06-10 16:24 ` Robert Milkowski [this message]
2020-06-24 8:54 ` James Pearson
2020-07-02 10:28 ` James Pearson
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='119601d63f43$9d55e860$d801b920$@gmail.com' \
--to=rmilkowski@gmail.com \
--cc=Anna.Schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=jcpearson@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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).