linux-kernel - Re: nfs mount failed with ipv6 addr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <174787036205.62796.16633284882232555223@noble.neil.brown.name>
Date: Thu, 22 May 2025 09:32:42 +1000
From: "NeilBrown" <neil@...wn.name>
To: "Yan, Haixiao (CN)" <haixiao.yan.cn@...driver.com>
Cc:
 chuck.lever@...cle.com, stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: nfs mount failed with ipv6 addr

On Thu, 22 May 2025, Yan, Haixiao (CN) wrote:
> On linux-5.10.y, my testcase run failed:
> 
> root@...el-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@...cle.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@...el-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@...el-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.............             .............done
> 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.....     .....done
> Writing inode tables:  0/13.....     .....done
> Writing superblocks and filesystem accounting information:  0/13.....     .....done
> root@...el-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mount /tmp/nfs.img /mnt
> 
> root@...el-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mkdir /mnt/nfs_root
> 
> root@...el-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# touch /etc/exports
> 
> root@...el-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# echo '/mnt/nfs_root *(insecure,rw,async,no_root_squash)' >> /etc/exports
> 
> root@...el-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

What does your "nfsserver" script do to try to stop/restart the nfsd?
For a very long time the approved way to stop nfsd has been to run
"rpc.nfsd 0".  My guess is that whatever script you are using still
trying to send a signal to nfsd.  That no longer works.

Unfortunately the various sysv-init scripts for starting/stopping nfsd
have never been part of nfs-utils so we were not able to update them.
nfs-utils *does* contain systemd unit files for sites which use systemd.

If you have a non-systemd way of starting/stopping nfsd, we would be
happy to make the relevant scripts part of nfs-utils so that we can
ensure they stay up to date.

Thanks,
NeilBrown