Re: NFSv2 directory cannot longer be exported in 3.14, 3.13 works fine

["Toralf Förster" <toralf.foerster@gmx.de>]

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

On 04/04/2014 11:57 PM, Toralf Förster wrote:
> At a user mode linux image (32 bit Gentoo Linux) the recent kernel gives this error while trying to mount a NFSv2 directory:
> mount.nfs: mount point /mnt/nfsv2 is not a directory
> 

A bisect points to :

6e14b46b91fee8a049b0940333ce13a820beaaa5 is the first bad commit
commit 6e14b46b91fee8a049b0940333ce13a820beaaa5
Author: Albert Fluegel <af@muc.de>
Date:   Mon Nov 18 12:18:01 2013 -0500

    nfsd: don't return high mode bits

    The Linux NFS server replies among other things to a "Check access permission"
    the following:

    NFS:    File type = 2 (Directory)
    NFS:    Mode = 040755

    A netapp server replies here:
    NFS:    File type = 2 (Directory)
    NFS:    Mode = 0755

    The RFC 1813 i read:
       fattr3

          struct fattr3 {
             ftype3     type;
             mode3      mode;
             uint32     nlink;
    ...
    For the mode bits only the lowest 9 are defined in the RFC

    As far as I can tell, knfsd has always done this, so apparently it's harmless.
    Nevertheless, it appears to be wrong.

    Note this is already correct in the NFSv4 case, only v2 and v3 need
    fixing.

    Signed-off-by: J. Bruce Fields <bfields@redhat.com>

:040000 040000 a60e55f5a9749db3977e12e8baa08d45fadba225 b982c02ec1069c5d969ccb71197e5569fe93b075 M fs

- -- 
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/

iF4EAREIAAYFAlM/9FcACgkQxOrN3gB26U5F1AD+JAP4cDM+rT9nk9Q8q681RywT
Ejxq7d0tnVUfWyDFDTgA/1sIUtpv9GSK8SeAJFu7oAhMt4e6eeIdbpMT2qUEQv6q
=Sles
-----END PGP SIGNATURE-----