From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andi Kleen <ak@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: NFS root broken in 2.6.18-rc2-mm1
Date: Thu, 03 Aug 2006 10:22:07 -0400 [thread overview]
Message-ID: <1154614928.5774.8.camel@localhost> (raw)
In-Reply-To: <200608020650.18093.ak@suse.de>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
On Wed, 2006-08-02 at 06:50 +0200, Andi Kleen wrote:
> FYI,
>
> I tried to boot 2.6.18-rc2-mm1 on a nfsroot system with x86-64 defconfig.
>
> Unfortunately it seems to generate lots of random EIO while reading executables
> during the startup sequence, which causes some things to break. Writing
> also doesn't seem to work - it complains about EPERM for that.
> Not all executables error out, but at least some.
>
> The same setup works fine with mainline 2.6.18-rc*
Known issue. The attached patch ought to fix it...
Cheers,
Trond
[-- Attachment #2: linux-2.6.18-036-nfs-fix_auth_mount.dif --]
[-- Type: message/rfc822, Size: 930 bytes --]
From: Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: No Subject
Date: Thu, 03 Aug 2006 10:21:56 -0400
Message-ID: <1154614916.5774.6.camel@localhost>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
---
fs/nfs/super.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/nfs/super.c b/fs/nfs/super.c
index 867b5dc..d744f63 100644
--- a/fs/nfs/super.c
+++ b/fs/nfs/super.c
@@ -471,9 +471,10 @@ static int nfs_validate_mount_data(struc
data->version);
return -EINVAL;
}
- /* Fill in pseudoflavor for mount version < 5 */
- data->pseudoflavor = RPC_AUTH_UNIX;
case 5:
+ /* Set the pseudoflavor */
+ if (!(data->flags & NFS_MOUNT_SECFLAVOUR))
+ data->pseudoflavor = RPC_AUTH_UNIX;
memset(data->context, 0, sizeof(data->context));
}
prev parent reply other threads:[~2006-08-03 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 4:50 NFS root broken in 2.6.18-rc2-mm1 Andi Kleen
2006-08-03 14:22 ` Trond Myklebust [this message]
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=1154614928.5774.8.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@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