mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yan, Haixiao (CN)" <haixiao.yan.cn@windriver.com>
To: chuck.lever@oracle.com
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: nfs mount failed with ipv6 addr
Date: Wed, 21 May 2025 22:11:16 +0800	[thread overview]
Message-ID: <6bb8f01e-628d-4353-8ed5-f77939e99df9@windriver.com> (raw)

On linux-5.10.y, my testcase run failed:

root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mount -t nfs [::1]:/mnt/nfs_root /mnt/v6 -o nfsvers=3
mount.nfs: requested NFS version or transport protocol is not supported

The first bad commit is:

commit 7229200f68662660bb4d55f19247eaf3c79a4217
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Mon Jun 3 10:35:02 2024 -0400

   nfsd: don't allow nfsd threads to be signalled.

   [ Upstream commit 3903902401451b1cd9d797a8c79769eb26ac7fe5 ]


Here is the test log:

root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# dd if=/dev/zero of=/tmp/nfs.img bs=1M count=100
100+0 records in
100+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 0.0386658 s, 2.7 GB/s
root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mkfs /tmp/nfs.img
mke2fs 1.46.1 (9-Feb-2021)
Discarding device blocks:   1024/102400\b\b\b\b\b\b\b\b\b\b\b\b\b             \b\b\b\b\b\b\b\b\b\b\b\b\bdone
Creating filesystem with 102400 1k blocks and 25688 inodes
Filesystem UUID: 77e3bc56-46bb-4e5c-9619-d9a0c0999958
Superblock backups stored on blocks:
	8193, 24577, 40961, 57345, 73729

Allocating group tables:  0/13\b\b\b\b\b     \b\b\b\b\bdone
Writing inode tables:  0/13\b\b\b\b\b     \b\b\b\b\bdone
Writing superblocks and filesystem accounting information:  0/13\b\b\b\b\b     \b\b\b\b\bdone
root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mount /tmp/nfs.img /mnt

root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mkdir /mnt/nfs_root

root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# touch /etc/exports

root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# echo '/mnt/nfs_root *(insecure,rw,async,no_root_squash)' >> /etc/exports

root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# /opt/wr-test/bin/svcwp.sh nfsserver restart
stopping mountd: done
stopping nfsd: ..........failed
  using signal 9:
..........failed
exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/mnt/nfs_root".
   Assuming default behaviour ('no_subtree_check').
   NOTE: this default has changed since nfs-utils version 1.0.x

starting 8 nfsd kernel threads: done
starting mountd: done
exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/mnt/nfs_root".
   Assuming default behaviour ('no_subtree_check').
   NOTE: this default has changed since nfs-utils version 1.0.x
root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# echo hello > /mnt/nfs_root/hello.txt

root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mkdir /mnt/v6

root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mount -t nfs [::1]:/mnt/nfs_root /mnt/v6 -o nfsvers=3
mount.nfs: requested NFS version or transport protocol is not supported

Thanks,
Haixiao


             reply	other threads:[~2025-05-21 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21 14:11 Yan, Haixiao (CN) [this message]
2025-05-21 15:03 ` Chuck Lever
2025-05-21 23:32 ` NeilBrown
2025-05-22  4:35   ` Haixiao Yan
2025-05-22 23:21     ` NeilBrown
2025-05-23  6:52       ` Yan, Haixiao (CN)
2025-05-23  7:42         ` NeilBrown
2025-05-23  9:00           ` Yan, Haixiao (CN)
2025-05-23 12:13             ` NeilBrown
2025-05-23 17:18               ` Yan, Haixiao (CN)

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=6bb8f01e-628d-4353-8ed5-f77939e99df9@windriver.com \
    --to=haixiao.yan.cn@windriver.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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®