On Tue, Apr 23, 2019 at 10:21:53AM +1000, NeilBrown wrote:
> On Sat, Apr 20 2019, Doug Nazar wrote:
>
> > After recently upgrading the kernel on one of my servers I was getting
> > the below crashes. Tracked it down to an NFSv3 root client, bisection
> > points to f875a792abe9. A revert of that on top of
> > 5.1.0-rc5-00289-gee2725f711fa works fine.
>
> hi Doug,
> thanks for the report and for bisecting!
>
> I think this bug has been fixed, but the fix hasn't landed upstream yet.
> If you
> git pull git://git.linux-nfs.org/~bfields/linux.git nfs-next
>
> you should get
>
> Commit 3c86794ac0e6 ("nfsd/nfsd3_proc_readdir: fix buffer count and page pointers")
>
> which should fix this.
>
>
> Bruce: I don't see that patch in your "for-5.1" branch, but you said
> "Queuing up for 5.1."
> Did something go awry?
Sorry, I've got this confusing system where I commit first to a branch
named for-x.y-incoming, then push it to for-x.y after I've tested it.
Except sometimes I forget to push to the for-x.y branch until the last
minute.
The -incoming branches should always be included in nfsd-next.
Anyway, I'll send a pull request now, it's overdue....
--b.
