From: Tony Lindgren <tony@atomide.com>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: Regression: SUNRPC: Use poll() to fix up the socket requeue races
Date: Tue, 26 Feb 2019 10:33:40 -0800 [thread overview]
Message-ID: <20190226183340.GD39872@atomide.com> (raw)
In-Reply-To: <9b9a6c5e34edea13b3ace42d39d97c27fd21c0db.camel@hammerspace.com>
Hi,
* Trond Myklebust <trondmy@hammerspace.com> [700101 00:00]:
> On Mon, 2019-02-25 at 22:27 +0000, Jon Hunter wrote:
> > On 25/02/2019 21:03, Trond Myklebust wrote:
> > This is nfsroot. I don't specify any particular NFS version from
> > the kernel cmdline, but this is seen with ARM kernel configs
> > tegra_defconfig and multi_v7_defconfig.
> >
> > Looking at the logs I am seeing the following crash which appears
> > to point to UDP ...
> >
> > [ 8.032956] Unable to handle kernel NULL pointer dereference at
> > virtual address 00000024
> > [ 8.041137] pgd = (ptrval)
> > [ 8.043858] [00000024] *pgd=00000000
> > [ 8.047437] Internal error: Oops: 5 [#1] SMP ARM
> > [ 8.052049] Modules linked in:
> > [ 8.055104] CPU: 1 PID: 100 Comm: kworker/u9:2 Not tainted 5.0.0-
> > rc7-next-20190222-g94a4752 #1
> > [ 8.063699] Hardware name: NVIDIA Tegra SoC (Flattened Device
> > Tree)
> > [ 8.069960] Workqueue: xprtiod xs_udp_data_receive_workfn
> > [ 8.075353] PC is at udp_poll+0x30/0x64
> > [ 8.079178] LR is at udp_poll+0x10/0x64
>
> Thanks! I see what the issue is now and I'll be fixing it ASAP.
I'm seeing this also with NFSroot. I can test the fix when available,
that is if you can please Cc me on the fix.
Thanks,
Tony
next prev parent reply other threads:[~2019-02-26 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 20:25 Regression: SUNRPC: Use poll() to fix up the socket requeue races Jon Hunter
2019-02-25 20:25 ` Jon Hunter
2019-02-25 21:03 ` Trond Myklebust
2019-02-25 22:27 ` Jon Hunter
2019-02-25 22:41 ` Trond Myklebust
2019-02-26 18:33 ` Tony Lindgren [this message]
2019-02-26 20:40 ` Trond Myklebust
2019-02-27 0:31 ` Tony Lindgren
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=20190226183340.GD39872@atomide.com \
--to=tony@atomide.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=trondmy@hammerspace.com \
/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.