From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Andrew Morton <akpm@osdl.org>
Cc: Helge Hafting <helgehaf@aitel.hist.no>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-rc5-mm1 nfs oddity, file creation => "no such file"
Date: Thu, 03 Mar 2005 11:35:10 +0100 [thread overview]
Message-ID: <4226E85E.6070407@aitel.hist.no> (raw)
In-Reply-To: <20050302133703.65e0b8f3.akpm@osdl.org>
Andrew Morton wrote:
>Helge Hafting <helgehaf@aitel.hist.no> wrote:
>
>
>>I observed an oddity on a nfs-mounted fs while using 2.6.11-rc5-mm1.
>>
>>
>
>Could you try this please?
>
>--- 25/fs/nfs/nfs3proc.c~nfsacl-acl-umask-handling-workaround-in-nfs-client-fix 2005-03-02 08:49:59.000000000 -0800
>+++ 25-akpm/fs/nfs/nfs3proc.c 2005-03-02 08:49:59.000000000 -0800
>@@ -423,6 +423,9 @@ exit:
> if (!inode)
> goto out;
> status = nfs3_set_default_acl(dir, inode, mode);
>+ if (status)
>+ goto out;
>+ return inode;
> }
> out:
> return ERR_PTR(status);
>_
>
>
>
"cat > some_new_file" worked fine on NFS with this patch. I'll keep using
nfs at work with this.
Helge Hafting
prev parent reply other threads:[~2005-03-03 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 19:14 2.6.11-rc5-mm1 nfs oddity, file creation => "no such file" Helge Hafting
2005-03-02 21:37 ` Andrew Morton
2005-03-03 10:35 ` Helge Hafting [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=4226E85E.6070407@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=akpm@osdl.org \
--cc=helgehaf@aitel.hist.no \
--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