On Wed, 04 Jan 2023, Trond Myklebust wrote:

If the server starts to reply NFS4ERR_STALE to GETATTR requests, why do
we care about stateid values? Just mark the inode as stale and drop it
on the floor.

We have a valid state from the server - we really shouldn't just ignore
it.

Maybe it would be OK to mark the inode stale.  I don't know if various
retry loops abort properly when the inode is stale.

If the server tries to declare the state as revoked, then it is clearly
borken, so let NetApp fix their own bug.

That's probably fair.

Thanks,
NeilBrown

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com