MIME-Version: 1.0
References: <CACH9xG8-tEtWstUVmD9eZFEEAqx-E8Gs14wDL+=uNtBK=-KJvQ@mail.gmail.com>
 <ZAmv57xeNqs7v9hY@kroah.com> <CACH9xG9=BFszD9OXspttTFdki0e68b5Hw7o11AUQ7pptSMy9wQ@mail.gmail.com>
 <ZAmzT/D8YxJ3844j@kroah.com>
In-Reply-To: <ZAmzT/D8YxJ3844j@kroah.com>
From:   Sylvain Menu <sylvain.menu@gmail.com>
Date:   Thu, 9 Mar 2023 16:24:48 +0100
Message-ID: <CACH9xG_v_2Y9d3Q16YB57Q5xVwSXe5FqLFSnjox6GotOT3DPmw@mail.gmail.com>
Subject: Re: nfs mount disappears due to inode revalidate failure
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     stable@vger.kernel.org, regressions@lists.linux.dev,
        chuck.lever@oracle.com, jlayton@kernel.org,
        linux-nfs@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

No I don't have that, I found the bug in production by no chance.
I tried to dive into the code but it quickly becomes complex for me,
at least it's easy to reproduce with a little script (while(1) timeout
my_c.code)

thanks
sylvain menu

Le jeu. 9 mars 2023 =C3=A0 11:22, Greg KH <gregkh@linuxfoundation.org> a =
=C3=A9crit :
>
> On Thu, Mar 09, 2023 at 11:17:30AM +0100, Sylvain Menu wrote:
> > I think it's a regression according to the old resolved bugs/tickets
> > but no idea since when it's broken again
>
> Any chance you can do 'git bisect' to find where it broke and what
> commit broke it?
>
> thanks,
>
> greg k-h