From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Sage Weil <sage@newdream.net>
Cc: akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, mszeredi@suse.cz, hch@lst.de,
mark.fasheh@oracle.com, trond.myklebust@fys.uio.no,
zach.brown@oracle.com
Subject: Re: [patch 01/12] vfs: fix vfs_rename_dir for FS_RENAME_DOES_D_MOVE filesystems
Date: Fri, 07 Aug 2009 14:00:07 +0900 [thread overview]
Message-ID: <87ws5gz0a0.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <Pine.LNX.4.64.0908062053560.26876@cobra.newdream.net> (Sage Weil's message of "Thu, 6 Aug 2009 21:05:17 -0700 (PDT)")
Sage Weil <sage@newdream.net> writes:
> FWIW, the originally proposed fix only rehashed on error, but Miklos was
> worried the rehash (under any circumstances) looked racy and/or bogus.
> And Al was just worried. See
>
> http://marc.info/?t=121580579500004&r=1&w=2
> and
> http://marc.info/?t=121664078900004&r=1&w=2
>
> The last word from Al (about this time last year :) was
>
> On Thu, 21 Aug 2008, Al Viro wrote:
>> I'm still not convinced that this is right. Let me finish review of the
>> current situation with dcache and rehashing, please. We definitely have
>> problems in that area; the question is how to deal with all that crap
>> without breaking exportfs *and* secondary roots a-la NFS ;-/
Thanks for pointer. I see.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2009-08-07 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 23:10 [patch 01/12] vfs: fix vfs_rename_dir for FS_RENAME_DOES_D_MOVE filesystems akpm
2009-08-07 1:36 ` OGAWA Hirofumi
2009-08-07 4:05 ` Sage Weil
2009-08-07 5:00 ` OGAWA Hirofumi [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=87ws5gz0a0.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=mszeredi@suse.cz \
--cc=sage@newdream.net \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@zeniv.linux.org.uk \
--cc=zach.brown@oracle.com \
/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