From: Hans-Peter Jansen <hpj@urpla.net>
To: Anthony Joseph Messina <amessina@messinet.com>,
Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: general protection fault, probably for non-canonical address in nfsd
Date: Mon, 08 Jun 2020 19:53:26 +0200 [thread overview]
Message-ID: <13519623.o9HzBvYcLm@xrated> (raw)
In-Reply-To: <2B6CBC8C-A1D4-4C39-AF45-958847C99572@oracle.com>
Am Montag, 8. Juni 2020, 17:28:53 CEST schrieb Chuck Lever:
> > On Jun 7, 2020, at 1:44 PM, Hans-Peter Jansen <hpj@urpla.net> wrote:
> >
> > Am Sonntag, 7. Juni 2020, 18:01:55 CEST schrieb Anthony Joseph Messina:
> >> On Sunday, June 7, 2020 10:32:44 AM CDT Hans-Peter Jansen wrote:
> >>> Hi,
> >>>
> >>> after upgrading the kernel from 5.6.11 to 5.6.14, we suffer from regular
> >>> crashes of nfsd here:
> >>>
> >>> 2020-06-07T01:32:43.600306+02:00 server rpc.mountd[2664]: authenticated
> >>> mount request from 192.168.3.16:303 for /work (/work)
> >>> 2020-06-07T01:32:43.602594+02:00 server rpc.mountd[2664]: authenticated
> >>> mount request from 192.168.3.16:304 for /work/vmware (/work)
> >>> 2020-06-07T01:32:43.602971+02:00 server rpc.mountd[2664]: authenticated
> >>> mount request from 192.168.3.16:305 for /work/vSphere (/work)
> >>> 2020-06-07T01:32:43.606276+02:00 server kernel: [51901.089211] general
> >>> protection fault, probably for non-canonical address 0xb9159d506ba40000:
> >>> 0000 [#1] SMP PTI 2020-06-07T01:32:43.606284+02:00 server kernel:
> >>> [51901.089226] CPU: 1 PID: 3190 Comm: nfsd Tainted: G O
> >>> 5.6.14-lp151.2-default #1 openSUSE Tumbleweed (unreleased)
> >>> 2020-06-07T01:32:43.606286+02:00 server kernel: [51901.089234] Hardware
> >>> name: System manufacturer System Product Name/P7F-E, BIOS 0906
> >>
> >> I see similar issues in Fedora kernels 5.6.14 through 5.6.16
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1839287
> >>
> >> On the client I mount /home with sec=krb5p, and /mnt/koji with sec=krb5
> >
> > Thanks for confirmation.
> >
> > Apart from the hassle with server reboots, this issue has some DOS
> > potential, I'm afraid.
>
> If you have a reproducer (even a partial one) then bisecting between a
> known good kernel and v5.6.14 (or 16) would be helpful.
I would love to bisect, but this is my primary production machine, that needs
to be up as much as possible. Apart from that, I'm about to leave the site for
a week and been severely time constrained for the next couple of weeks..
Sorry.
Anthony?
--
Pete
next prev parent reply other threads:[~2020-06-08 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 15:32 general protection fault, probably for non-canonical address in nfsd Hans-Peter Jansen
2020-06-07 16:01 ` Anthony Joseph Messina
2020-06-07 17:44 ` Hans-Peter Jansen
2020-06-08 15:28 ` Chuck Lever
2020-06-08 17:53 ` Hans-Peter Jansen [this message]
2020-06-08 18:31 ` Anthony Joseph Messina
2020-06-08 19:27 ` Chuck Lever
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=13519623.o9HzBvYcLm@xrated \
--to=hpj@urpla.net \
--cc=amessina@messinet.com \
--cc=chuck.lever@oracle.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.