Re: nfs mount disappears due to inode revalidate failure

From: Greg KH <gregkh@linuxfoundation.org>
To: Sylvain Menu <sylvain.menu@gmail.com>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
	chuck.lever@oracle.com, jlayton@kernel.org,
	linux-nfs@vger.kernel.org
Subject: Re: nfs mount disappears due to inode revalidate failure
Date: Thu, 9 Mar 2023 11:07:35 +0100	[thread overview]
Message-ID: <ZAmv57xeNqs7v9hY@kroah.com> (raw)
In-Reply-To: <CACH9xG8-tEtWstUVmD9eZFEEAqx-E8Gs14wDL+=uNtBK=-KJvQ@mail.gmail.com>

On Thu, Mar 09, 2023 at 10:42:41AM +0100, Sylvain Menu wrote:
> Hello,
> 
> I am writing to report an issue on a nfs mount that disappears due to
> an inode revalide failure (already sent in January but probably banned
> with html format...).
> This very old commit
> (https://github.com/torvalds/linux/commit/cc89684c9a265828ce061037f1f79f4a68ccd3f7)
> exactly show the problem I have and this old resolved issue
> (https://bugzilla.kernel.org/show_bug.cgi?id=117651) is probably
> failing again today
> 
> To sum up, I have a NFS mount inside another NFS mount (for example:
> /opt/nfs/mount1 & /opt/nfs/mount1/mount2).
> If I kill a task trying to get a file descriptor on
> /opt/nfs/mount1/mount2 then it will be unmounted. My simple test code
> to reproduce very easily:
> 
> int main(int argc, char *argv[]) {
>     while (1) {
>         close(open(argv[1], O_RDONLY));
>     }
> }
> 
> In logs, I have: "nfs_revalidate_inode: (0:62/845965) getattr failed,
> error=-512"
> 
> Tested on 5.19 and 6.1 kernel

So is this a regression or something that has always been present?

thanks,

greg k-h