From: "J. Bruce Fields" <bfields@fieldses.org>
To: Damjan Georgievski <gdamjan@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfsd crash with 4.6 and 4.7 (bisected)
Date: Sat, 18 Jun 2016 09:29:55 -0400 [thread overview]
Message-ID: <20160618132955.GD9980@fieldses.org> (raw)
In-Reply-To: <CAEk1YH6crPwzVAOBv+swq2K9hNsH9W-RW-_kwyz=dMC+kWeEPQ@mail.gmail.com>
On Sat, Jun 18, 2016 at 12:04:32PM +0200, Damjan Georgievski wrote:
> >> I'm experiencing a kernel crash with the kernel nfs daemon in 4.6.1,
> >> 4.6.2 and 4.7.0-rc3-g5edb564
> >> 4.5.4 is ok.
> >>
> >> My server is ArchLinux, nothing special, nfs-server.service enabled,
> >> this in exports:
> >> /home/nfs/archlinux-rpi
> >> 192.168.15.0/24(rw,no_subtree_check,nohide,insecure,no_root_squash,async)
> >>
> >> The client is a raspberrypi with 4.4.13-2-ARCH kernel, a nfs root,
> >> ArchLinuxArm and this kernel cmdline:
> >> nfsroot=192.168.15.103:/home/nfs/archlinux-rpi,vers=4.2,proto=tcp,rsize=1048576,wsize=1048576
> >>
> >> the crash happens every time I *reboot* the raspberrypi. just booting
> >> it in the first place doesn't crash the server.
> >> please cc me for other info, since I'm not subscribed.
> >
> > Could you check latest upstream? I think there's a good chance this is
> > fixed by 39a9beab5acb "rpc: share one xps between all backchannels".
>
> thanks Bruce,
> 4.7.0-rc3-gbb96727 seems to work fine.
>
> I hope this gets submitted to stable too?
Yes, the "Cc: stable@vger.kernel.org" should make that happen, though it
may take some time for them to get to it.
--b.
prev parent reply other threads:[~2016-06-18 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 10:02 nfsd crash with 4.6 and 4.7 (bisected) Damjan Georgievski
2016-06-17 19:12 ` J. Bruce Fields
2016-06-18 10:04 ` Damjan Georgievski
2016-06-18 13:29 ` J. Bruce Fields [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160618132955.GD9980@fieldses.org \
--to=bfields@fieldses.org \
--cc=gdamjan@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.