From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] Re: [RFC] yet another knfsd-reiserfs patch
Date: 02 Jun 2001 00:19:59 +0200 [thread overview]
Message-ID: <shssnhj267k.fsf@charged.uio.no> (raw)
In-Reply-To: <134680000.991430407@tiny>
In-Reply-To: Chris Mason's message of "Fri, 01 Jun 2001 17:20:07 -0400"
Hi Chris,
Do you really need the parent inode in the filehandle?
That screws rename up pretty badly, since the filehandle changes when
you rename into a different directory. It means for instance that when
I do
open(foo)
mv foo bar/
write (foo)
close(foo)
then I have a pretty good chance of getting an ESTALE on the write()
statement.
Cheers,
Trond
next prev parent reply other threads:[~2001-06-01 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 14:45 [RFC] yet another knfsd-reiserfs patch Chris Mason
2001-05-01 1:18 ` Chris Mason
2001-06-01 21:20 ` Chris Mason
2001-06-01 22:19 ` Trond Myklebust [this message]
2001-06-02 17:00 ` [NFS] " Chris Mason
2001-06-02 6:17 ` Hans Reiser
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=shssnhj267k.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=nfs@lists.sourceforge.net \
/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