From: Olaf Kirch <okir@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: nfs@lists.sourceforge.net, Paul Szabo <psz@maths.usyd.edu.au>
Subject: Re: #255931 NFS fh_verify causes lost output
Date: Thu, 19 Aug 2004 10:30:14 +0200 [thread overview]
Message-ID: <20040819083014.GA4739@suse.de> (raw)
In-Reply-To: <20040818210041.A2223@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
On Wed, Aug 18, 2004 at 09:00:41PM +0100, Christoph Hellwig wrote:
> We have the following report from Paul Szabo in the Debian bugtracking system,
> any chance someone could look into it? The RedHat bugzilla reference is quite
> interesting aswell.
I reported exactly this problem here a few months ago; the fix I proposed
was to return EACCES rather than ESTALE in find_exported_dentry()
(fs/exportfs/expfs.c). Not sure what happened to this patch; seems it
fell through the cracks.
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
[-- Attachment #2: subtreecheck-nostale.patch --]
[-- Type: text/plain, Size: 657 bytes --]
--- linux-2.6.5/fs/exportfs/expfs.c.nostale 2004-04-04 05:37:44.000000000 +0200
+++ linux-2.6.5/fs/exportfs/expfs.c 2004-04-30 10:32:19.000000000 +0200
@@ -278,7 +278,15 @@
/* drat - I just cannot find anything acceptable */
dput(result);
- return ERR_PTR(-ESTALE);
+
+ /* Originally, we would return ESTALE here. This is not
+ * correct, however, as the file handle is valid; it just
+ * failed our acceptance test.
+ * This will lead to unexpected results in the client if
+ * there are two processes accessing the same file; one
+ * with proper permissions and one without.
+ */
+ return ERR_PTR(-EACCES);
err_target:
dput(target_dir);
next prev parent reply other threads:[~2004-08-19 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 20:00 #255931 NFS fh_verify causes lost output Christoph Hellwig
2004-08-19 8:30 ` Olaf Kirch [this message]
2004-08-20 2:30 ` Neil Brown
2004-08-20 9:44 ` Olaf Kirch
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=20040819083014.GA4739@suse.de \
--to=okir@suse.de \
--cc=hch@infradead.org \
--cc=nfs@lists.sourceforge.net \
--cc=psz@maths.usyd.edu.au \
/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.