public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Mayhew <smayhew@redhat.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	linux-nfs@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Howells <dhowells@redhat.com>,
	Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [BISECT BUG] NFS v4 root not working after 6d972518b821 ("NFS: Add fs_context support.")
Date: Thu, 16 Jan 2020 19:49:15 -0500	[thread overview]
Message-ID: <20200117004915.GA3111@aion.usersys.redhat.com> (raw)
In-Reply-To: <CAJKOXPeCVwZfBsCVbc9RQUGi0UfWQw0uFamPiQasiO8fSthFsQ@mail.gmail.com>

On Thu, 16 Jan 2020, Krzysztof Kozlowski wrote:

> Hi all,
> 
> Bisect pointed to 6d972518b821 ("NFS: Add fs_context support.") for
> failures of mounting NFS v4 root on my boards:
> mount.nfs4 -o vers=4,nolock 192.168.1.10:/srv/nfs/odroidhc1 /new_root
> [ 24.980839] NFS4: Couldn't follow remote path
> [ 24.986201] NFS: Value for 'minorversion' out of range
> mount.nfs4: Numerical result out of range
> 
> https://krzk.eu/#/builders/21/builds/1692
> Full console log:
> https://krzk.eu/#/builders/21/builds/1692/steps/14/logs/serial0
> 
> Enabling NFS v4.1 in defconfig seems to help. I can send patches for
> this (for defconfigs) but probably the root cause should be fixed as
> well.
> 
> Environment:
> 1. Arch ARM Linux
> 2. exynos_defconfig
> 3. Exynos boards (Odroid XU3, etc), ARMv7, octa-core (Cortex-A7+A15),
> Exynos5422 SoC
> 4. systemd, boot up with static IP set in kernel command line
> 5. No swap
> 6. Kernel, DTB and initramfs are downloaded with TFTP
> 7. NFS root from NFSv4 server
> 
> Let me know if you need more details.

I haven't had much luck reproducing this.  I disabled v4.1 in my .config
and I can still boot a VM with NFS root (granted, I don't really use NFS
root so this setup is brand new and pretty basic):

[root@localhost ~]# cat /proc/cmdline
BOOT_IMAGE=mountapi/vmlinuz initrd=mountapi/initrd.img ip=dhcp selinux=0 console=tty0 console=ttyS0,115200 root=nfs4:192.168.122.3:/export/nfsroot/fedora31

[root@localhost ~]# grep nfs /proc/mounts
192.168.122.3:/export/nfsroot/fedora31 / nfs rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.69,local_lock=none,addr=192.168.122.3 0 0

Just out of curiousity, what version of the mount.nfs program do you
have in your initramfs?  I'm wondering if it's maybe passing the mount
options differently than mine.  FWIW I'm using version 2.4.2:

[smayhew@aion tmp]$ lsinitrd /var/lib/tftpboot/mountapi/initrd.img|grep mount.nfs
-rwsr-xr-x   1 root     root       208600 Feb 14  2019 usr/sbin/mount.nfs
lrwxrwxrwx   1 root     root            9 Feb 14  2019 usr/sbin/mount.nfs4 -> mount.nfs
[smayhew@aion tmp]$ /usr/lib/dracut/skipcpio /var/lib/tftpboot/mountapi/initrd.img|zcat|cpio -id usr/sbin/mount.nfs
256163 blocks
[smayhew@aion tmp]$ ./usr/sbin/mount.nfs -V
mount.nfs: (linux nfs-utils 2.4.2)
[smayhew@aion tmp]$

-Scott

> 
> Best regards,
> Krzysztof
> 


  reply	other threads:[~2020-01-17  0:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 11:33 [BISECT BUG] NFS v4 root not working after 6d972518b821 ("NFS: Add fs_context support.") Krzysztof Kozlowski
2020-01-17  0:49 ` Scott Mayhew [this message]
2020-01-17 11:53   ` Krzysztof Kozlowski
2020-01-17 12:54 ` David Howells
2020-01-17 13:16   ` Krzysztof Kozlowski
2020-01-17 14:08     ` David Howells
2020-01-17 14:36       ` Krzysztof Kozlowski
2020-01-17 14:20 ` David Howells
2020-01-17 14:40   ` Krzysztof Kozlowski
2020-01-17 15:12     ` David Howells
2020-01-17 15:17       ` Trond Myklebust
2020-01-17 15:32         ` Scott Mayhew
2020-01-17 15:44         ` David Howells
2020-01-17 15:48     ` [PATCH] nfs: Return EINVAL rather than ERANGE for mount parse errors David Howells
2020-01-17 15:55       ` [PATCH v2] " David Howells
2020-01-17 16:51         ` Krzysztof Kozlowski
2020-01-17 17:18           ` David Howells
2020-01-17 20:21             ` Schumaker, Anna
2020-01-17 21:12               ` David Howells

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=20200117004915.GA3111@aion.usersys.redhat.com \
    --to=smayhew@redhat.com \
    --cc=anna.schumaker@netapp.com \
    --cc=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.com \
    --cc=viro@zeniv.linux.org.uk \
    /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