From: Chuck Lever III <chuck.lever@oracle.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: linux 5.13 kernel regression for NFS server
Date: Tue, 29 Jun 2021 13:01:13 +0000 [thread overview]
Message-ID: <CB1159AE-7C7F-402C-9F52-954FFAEAAEE8@oracle.com> (raw)
In-Reply-To: <004d01d76cd3$18db1830$4a914890$@lucidpixels.com>
Hi Justin-
> On Jun 29, 2021, at 6:39 AM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
> Hello,
>
> ISSUE: Can no longer mount NFS server(5.13) share.
> WORKAROUND: Reverting back to the 5.13-rc7 kernel for the NFS server, all
> clients can then mount the share.
>
> Kernel 5.13 vs. 5.13-rc7 for x86_64
>
> With Kernel 5.13-rc7:
>
> ## mount is successful (from multiple clients, phone, tv, other Linux
> client)
> # mount 192.168.1.2:/r1 /r1
> #
>
> With Kernel 5.13 (hangs from multiple clients, phone, tv, other Linux
> client)
>
> ## mount hangs:
> # mount 192.168.1.2:/r1 /r1
>
> (strace output where it is hanging)
> ...
> clone(child_stack=NULL,
> flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
> child_tidptr=0x7f2285e303d0) = 1741
> wait4(1741, 0x7ffeaab6ce08, 0, NULL) = ? ERESTARTSYS (To be restarted if
> SA_RESTART is set)
> --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
> wait4(1741,
>
> No user changes in the kernel .config other than the comment for the version
> text:
>
> --- config-20210628.1624867695 2021-06-28 04:08:15.152781940 -0400
> +++ config-20210628.1624867962 2021-06-28 04:12:42.591981706 -0400
> @@ -1,6 +1,6 @@
> #
> # Automatically generated file; DO NOT EDIT.
> -# Linux/x86 5.13.0-rc7 Kernel Configuration
> +# Linux/x86 5.13.0 Kernel Configuration
> #
> CONFIG_CC_VERSION_TEXT="gcc (Debian 10.2.1-6) 10.2.1 20210110"
> CONFIG_CC_IS_GCC=y
It's likely this regression is due to a last minute change to
alloc_pages_bulk_array() done just before v5.13. See:
https://lore.kernel.org/linux-nfs/20210629081432.GE3840@techsingularity.net/T/#t
for details.
--
Chuck Lever
next prev parent reply other threads:[~2021-06-29 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 10:39 Justin Piszcz
2021-06-29 13:01 ` Chuck Lever III [this message]
2021-07-07 14:03 ` Justin Piszcz
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=CB1159AE-7C7F-402C-9F52-954FFAEAAEE8@oracle.com \
--to=chuck.lever@oracle.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®