From: Trond Myklebust <trondmy@hammerspace.com>
To: "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: Mon, 25 Feb 2019 21:03:48 +0000 [thread overview]
Message-ID: <ab485d7ba4f9603850b81e6c2242dc25026eabcb.camel@hammerspace.com> (raw)
In-Reply-To: <95702994-6762-e42b-06ee-ae945c2137bd@nvidia.com>
On Mon, 2019-02-25 at 20:25 +0000, Jon Hunter wrote:
> Hi Trond,
>
> Starting in next-20190222 I have observed a regression with NFS
> causing
> some of our boards to fail to boot. Bisect points to your commit ...
>
> commit 0ffe86f48026b7f34db22d1004bc9992f0db8b33
> Author: Trond Myklebust <trond.myklebust@hammerspace.com>
> Date: Wed Jan 30 14:51:26 2019 -0500
>
> SUNRPC: Use poll() to fix up the socket requeue races
>
>
> After reverting this on top of -next I no longer see the problem. I
> have
> not had chance to look any closer, but wanted to see if you had any
> ideas what might be the problem.
>
> Cheers
> Jon
What kind of boot is this? UDP or TCP? nfsroot? NFSv3 or NFSv4?
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2019-02-25 21:04 UTC|newest]
Thread overview: 7+ 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 21:03 ` Trond Myklebust [this message]
2019-02-25 22:27 ` Jon Hunter
2019-02-25 22:41 ` Trond Myklebust
2019-02-26 18:33 ` Tony Lindgren
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=ab485d7ba4f9603850b81e6c2242dc25026eabcb.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-tegra@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox