On Sat, Jan 13, 2024 at 10:35:09AM +0100, Greg KH wrote:
> On Thu, Jan 11, 2024 at 12:26:39PM -0500, Jeff Layton wrote:
> > On Thu, 2024-01-11 at 10:30 +0100, Greg KH wrote:
> > > On Thu, Jan 11, 2024 at 07:20:02PM +1100, email200202 wrote:
> > > > Reverting the following 3 commits fixed the problem in kernel 6.1.71:
> > > >
> > > > f9a01938e07910224d4a2fd00583725d686c3f38
> > > > bb4f791cb2de1140d0fbcedfe9e791ff364021d7
> > > > 03d68ffc48b94cc1e15bbf3b4f16f1e1e4fa286a
> > >
> > > When sending us git ids, please show the full context so we have a hint
> > > as to what they are. For this, it should be:
> > >
> > > f9a01938e079 ("NFSD: fix possible oops when nfsd/pool_stats is closed.")
> > > bb4f791cb2de ("nfsd: call nfsd_last_thread() before final nfsd_put()")
> > > 03d68ffc48b9 ("nfsd: separate nfsd_last_thread() from nfsd_put()")
> > >
> > > Do you also have these issues in the latest 6.6.y release? 6.7?
> > >
> > >
> >
> > I wasn't able to reproduce the exact same bug as the reporter, but I did
> > see a different panic due to the above patches. Some of those fixes
> > aren't appropriate without pulling in earlier commits, but I think it's
> > probably best to just drop these two:
> >
> > bb4f791cb2de ("nfsd: call nfsd_last_thread() before final nfsd_put()")
> > 03d68ffc48b9 ("nfsd: separate nfsd_last_thread() from nfsd_put()")
> >
> > Greg, does that sound OK?
>
> Sure, can you send reverts for them, or do you need me to make them?
Nevermind, I made them, thanks.
greg k-h
