Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
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>
References: <0aee01d63d91$1f104300$5d30c900$@gmail.com> <7E441550-FCCF-492E-BACB-271A42D4A6C4@oracle.com>
In-Reply-To: <7E441550-FCCF-492E-BACB-271A42D4A6C4@oracle.com>
Subject: RE: NFSv4.0: client stuck looping on RENEW + NFSERR_STALE_CLIENTID
Date:   Wed, 10 Jun 2020 17:24:28 +0100
Message-ID: <119601d63f43$9d55e860$d801b920$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
        charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thread-Index: AQE7uIdLFcOyEELuFPvOfhLxfxPnHwHtyK3jqfenTBA=
Content-Language: en-gb
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

> 
> 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