linux-kernel - Re: NFS V4 calls for a NFS v3 mount

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: <53419674.7010509@gmx.de>
Date:	Sun, 06 Apr 2014 20:01:24 +0200
From:	Toralf Förster <toralf.foerster@....de>
To:	Roger Heflin <rogerheflin@...il.com>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: NFS V4 calls for a NFS v3 mount

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 04/06/2014 07:57 PM, Roger Heflin wrote:
> No where in the mount command did you tell it that this was a 
> nfsversion 3 only mount, the mount name itself means nothing to
> mount, so it tired nfs version 4 first then nfs version 3.
> 
> Note this in the man page for nfs: nfsvers=n      The NFS protocol
> version number used to contact the server's NFS service.  If the
> server does  not  support the  requested  version, the mount
> request fails.  If this option is not specified, the client
> negotiates a suitable version with the server, trying version 4
> first, version 3 second, and version 2 last.
> 

ick, I misunderstand the key word "nfs4" in /etc/fstab - I thought
that (and only that) would activate any NFS v4 Calls :

Hre all of my setting
$ grep nfs /etc/fstab
n22:/mnt/ramdisk    /mnt/nfsv2      nfs     auto,bg,intr,soft,nfsvers=2
n22:/mnt/ramdisk    /mnt/nfsv3      nfs     auto,bg,intr,soft
n22:                /mnt/nfsv4      nfs4    auto,bg,intr,soft


Thx for explanation.


> On Sun, Apr 6, 2014 at 12:27 PM, Toralf Förster
> <toralf.foerster@....de> wrote: Probably a question better suited
> for a NFS noobs mailing list (is there any around ?) ...
> 
> While playing with kernel 3.13.x, wireshark and NFS I realized,
> that mounting a NFS v3 share results in NFS V4 Calls - is this
> indented or a wireshark dissector issue ?
> 
> 
> $ cat /etc/exports # /etc/exports: NFS file systems being exported.
> See exports(5). /mnt/ramdisk
> 192.168.0.0/16(rw,fsid=0,insecure,no_subtree_check,async,no_root_squash)
>
> 
> 
> $ grep nfsv3 /etc/fstab n22:/mnt/ramdisk    /mnt/nfsv3      nfs
> auto,bg,intr,soft
> 
- -- 
MfG/Sincerely
Toralf Förster
pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlNBlnQACgkQxOrN3gB26U41HQD8D/KROgItC324iDevD33vJ6QS
PcSWPcBTzimC0cMOfzkA/04ejAWOGGqyqNedV5Ps235rxqbxDWoiUS7M7iQtu/Wz
=jJAD
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/