From: Jeff Layton <jlayton@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NFSv2 directory cannot longer be exported in 3.14, 3.13 works fine
Date: Sat, 5 Apr 2014 08:51:43 -0400 [thread overview]
Message-ID: <20140405085143.59e578ff@tlielax.poochiereds.net> (raw)
In-Reply-To: <533FF457.5080907@gmx.de>
On Sat, 05 Apr 2014 14:17:27 +0200
Toralf Förster <toralf.foerster@gmx.de> wrote:
> -----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-----
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
This was already tracked down earlier this week. Bruce has a patch
queued to fix it in his nfsd-next branch. See this thread from earlier
this week:
Subject: Re: linux-3.14 nfsd regression
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2014-04-05 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <533F2ABF.2030107@gmx.de>
2014-04-05 12:17 ` Toralf Förster
2014-04-05 12:51 ` Jeff Layton [this message]
2014-04-05 13:23 ` Toralf Förster
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=20140405085143.59e578ff@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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®