All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Mark Lord <mlord@pobox.com>,
	"J. Bruce Fields" <bfields@redhat.com>,
	Albert Fluegel <af@muc.de>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-3.14 nfsd regression
Date: Fri, 4 Apr 2014 09:58:43 -0400	[thread overview]
Message-ID: <20140404135842.GB17594@fieldses.org> (raw)
In-Reply-To: <20140403192146.79679909@tlielax.poochiereds.net>

On Thu, Apr 03, 2014 at 07:21:46PM -0400, Jeff Layton wrote:
> So according to the RFC you have to encode both the mode bits and the
> ftype for v2. The type bits seem to be removed from the mode in NFSv3
> though, so perhaps we should only be doing that masking in versions
> above v2?

Right, the problematic patch applied the same mask in both v2 and v3
cases, so I'm reverting just the v2 part (see below).

> With a quick check, it looks like the v3 code doesn't rely on those bits
> and I imagine v4 doesn't either.
> 
> It might also be nice to have the client v2 decode_fattr function to
> throw a warning if the server sends us mismatched type bits and ftype
> values. That would have helped us catch this sooner...

Yes, that might be a reasonable thing to do, though I don't know if it's
worth it.

--b.

commit 35a8dff14e76c00e5b52140290cfb498dc2454a0
Author: J. Bruce Fields <bfields@redhat.com>
Date:   Thu Apr 3 15:10:35 2014 -0400

    nfsd: revert v2 half of "nfsd: don't return high mode bits"
    
    This reverts the part of commit 6e14b46b91fee8a049b0940333ce13a820beaaa5
    that changes NFSv2 behavior.
    
    Mark Lord found that it broke nfs-root for Linux clients, because it
    broke NFSv2.
    
    In fact, from RFC 1094:
    
    	"Notice that the file type is specified both in the mode bits
    	and in the file type.  This is really a bug in the protocol and
    	will be fixed in future versions."
    
    So NFSv2 clients really are expected to depend on the high bits of the
    mode.
    
    Cc: stable@kernel.org
    Reported-by: Mark Lord <mlord@pobox.com>
    Signed-off-by: J. Bruce Fields <bfields@redhat.com>

diff --git a/fs/nfsd/nfsxdr.c b/fs/nfsd/nfsxdr.c
index b17d932..9c769a4 100644
--- a/fs/nfsd/nfsxdr.c
+++ b/fs/nfsd/nfsxdr.c
@@ -152,7 +152,7 @@ encode_fattr(struct svc_rqst *rqstp, __be32 *p, struct svc_fh *fhp,
 	type = (stat->mode & S_IFMT);
 
 	*p++ = htonl(nfs_ftypes[type >> 12]);
-	*p++ = htonl((u32) (stat->mode & S_IALLUGO));
+	*p++ = htonl((u32) stat->mode);
 	*p++ = htonl((u32) stat->nlink);
 	*p++ = htonl((u32) from_kuid(&init_user_ns, stat->uid));
 	*p++ = htonl((u32) from_kgid(&init_user_ns, stat->gid));

  reply	other threads:[~2014-04-04 13:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 16:33 linux-3.14 nfsd regression Mark Lord
2014-04-03 16:44 ` Mark Lord
2014-04-03 16:53   ` Mark Lord
2014-04-03 17:16 ` J. Bruce Fields
2014-04-03 17:51   ` Mark Lord
2014-04-03 18:02     ` /proc/slab_allocators question Pietro Paolini
2014-04-03 18:55     ` linux-3.14 nfsd regression Jeff Layton
2014-04-03 20:16       ` J. Bruce Fields
2014-04-03 23:21         ` Jeff Layton
2014-04-04 13:58           ` J. Bruce Fields [this message]
2014-04-04 14:07             ` Jeff Layton
2014-05-01 11:50             ` Mark Lord
2014-05-01 19:59               ` J. Bruce Fields
2014-04-03 19:30     ` J. Bruce Fields
2014-04-03 20:11       ` J. Bruce Fields
2014-04-03 20:48       ` Mark Lord
2014-04-03 21:28         ` J. Bruce Fields
2014-04-03 21:32           ` Mark Lord
2014-04-03 20:15     ` J. Bruce Fields
2014-04-03 20:51       ` Mark Lord

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=20140404135842.GB17594@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=af@muc.de \
    --cc=bfields@redhat.com \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mlord@pobox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.