linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <mlord@pobox.com>
To: Albert Fluegel <af@muc.de>, "J. Bruce Fields" <bfields@redhat.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-3.14 nfsd regression
Date: Thu, 03 Apr 2014 12:53:50 -0400	[thread overview]
Message-ID: <533D921E.4030001@pobox.com> (raw)
In-Reply-To: <533D8FE9.80309@pobox.com>

Mark Lord wrote:
> On 14-04-03 12:33 PM, 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.
> ..
> 
> 
> Looking into the (previously attached) trace, the bits that seem to be
> getting chopped most often are S_IFREG (0x8000) and S_IFDIR (0x4000).
> It appears that one/both of those are needed for mounting nfsroot.
> 
> 
> [ 2733.823753] encode_fattr: mode=0x000041ed mask=0x00000fff
> [ 2733.824217] encode_fattr: mode=0x000041ed mask=0x00000fff
> [ 2733.838769] encode_fattr: mode=0x000041ed mask=0x00000fff
> [ 2733.839175] encode_fattr: mode=0x0000a1ff mask=0x00000fff
> [ 2733.839895] encode_fattr: mode=0x000081ed mask=0x00000fff
...

Okay, the NFS root filesystem mounts and appears to work if I use this:

    *p++ = htonl((u32) (stat->mode & (S_IALLUGO | S_IFDIR | S_IFREG | S_IFCHR)));

But I suspect it may also need S_IFBLK for block device accesses as well.

Cheers


  reply	other threads:[~2014-04-03 16:53 UTC|newest]

Thread overview: 19+ 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 [this message]
2014-04-03 17:16 ` J. Bruce Fields
2014-04-03 17:51   ` Mark Lord
2014-04-03 18:55     ` 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
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=533D921E.4030001@pobox.com \
    --to=mlord@pobox.com \
    --cc=af@muc.de \
    --cc=bfields@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).