From: "J. Bruce Fields" <bfields@redhat.com>
To: Mark Lord <mlord@pobox.com>
Cc: Albert Fluegel <af@muc.de>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-3.14 nfsd regression
Date: Thu, 3 Apr 2014 17:28:41 -0400 [thread overview]
Message-ID: <20140403212841.GM28790@pad.redhat.com> (raw)
In-Reply-To: <533DC90B.8050906@pobox.com>
On Thu, Apr 03, 2014 at 04:48:11PM -0400, Mark Lord wrote:
> On 14-04-03 03:30 PM, J. Bruce Fields wrote:
> > On Thu, Apr 03, 2014 at 01:51:06PM -0400, Mark Lord wrote:
> >> On 14-04-03 01:16 PM, J. Bruce Fields wrote:
> >>> On Thu, Apr 03, 2014 at 12:33:55PM -0400, Mark Lord wrote:
> >>>> This commit from linux-3.14 breaks our NFS-root clients here:
> >>>>
> >>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6e14b46b91fee8a049b0940333ce13a820beaaa5
> >>>>
> >>>>
> >>>> - *p++ = htonl((u32) stat->mode);
> >>>> + *p++ = htonl((u32) (stat->mode & S_IALLUGO));
> >>>>
> >>>>
> >>>> Reverting the one-liner above (on the server) fixes it for us,
> >>>> as does reverting back to linux-3.13.8 on the server.
> >>>>
> >>>> The NFS-root clients are on PowerPC (big-endian) architecture,
> >>>> running linux-3.12.16. The NFS server is on an Intel PC running linux-3.14.
> >>>>
> >>>> ACL is completely disabled on server and client,
> >>>> and we're using NFSv2/v3. No support for v4.
> >>>>
> >>>> I instrumented the function to see what other bits were being cleared
> >>>> by the (stat->mode & S_IALLUGO) masking. The results are attached.
> >>>
> >>> Hm, it sounds like a bug in the client if it's depending on those high
> >>> bits.
> >>
> >> But only for mounting / starting up from the nfsroot, it seems.
> >> I wonder if there's an unusual code path for that in there?
> >> The regular stuff looks mostly fine:
> >>
> >> p = xdr_decode_ftype3(p, &fmode);
> >> fattr->mode = (be32_to_cpup(p++) & ~S_IFMT) | fmode;
> >
> > Hm, but that's in nfs3xdr.c; in nfs2xdr.c we have just
> >
> > fattr->mode = be32_to_cpup(p+);
> >
> > and NFSv2 is the default for nfsroot. Do you have some reason to
> > believe you're not using NFSv2?
>
> Oh, the client here was using NFS2, absolutely.
> I just don't know my way around the code very well yet. :)
>
> But that mask in nfs3xdr.c (client) doesn't match what the server side is using.
Not sure there's anything to see there.
Looking at include/uapi/linux/stat.h and include/linux/stat.h, if I'm
doing this right...
S_ISFMT is 0170000
S_IALLUGO is 0007777
So they're 16-bit complements. And we're storing the result in a short?
--b.
next prev parent reply other threads:[~2014-04-03 21:28 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
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 [this message]
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=20140403212841.GM28790@pad.redhat.com \
--to=bfields@redhat.com \
--cc=af@muc.de \
--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.