From: Ian Kent <raven@themaw.net>
To: Sage Weil <sage@newdream.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Erez Zadok <ezk@cs.sunysb.edu>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
rdreier@cisco.com, kirkland@canonical.com,
tyhicks@linux.vnet.ibm.com
Subject: Re: [patch 4/9] vfs: add lockdep annotation to s_vfs_rename_key for ecryptfs
Date: Wed, 02 Dec 2009 09:40:08 +0800 [thread overview]
Message-ID: <4B15C578.8030503@themaw.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0912011636200.5806@cobra.newdream.net>
Sage Weil wrote:
> On Tue, 1 Dec 2009, Andrew Morton wrote:
>> Quite a VFS patch backlog here, some held over from 2.6.32:
>>
>> vfs-fix-vfs_rename_dir-for-fs_rename_does_d_move-filesystems.patch
>
> This problem will bite ceph without this patch. I could work around it,
> but it would be nice to fix the real bug. Al was worried about nfs:
>
>> It's _probably_ OK now, but I'd really like to think about NFS
>> behaviour. There are subtle traps in that area.
>
> http://marc.info/?l=linux-kernel&m=121666695629006&w=2
>
>> vfs-make-real_lookup-do-dentry-revalidation-with-i_mutex-held.patch
>> vfs-clean-up-real_lookup.patch
>
> These were waiting on the autofs4 locking changes and legacy autofs
> removal, which Ian has posted and appear to be ready.
That's right.
The locking changes were sent to Andrew some time ago and they are
present in the mm kernel.
I've been side tracked and only recently posted the autofs removal
patches, no-one objected and I need to send them to Andrew, as in my
normal process.
Ian
next prev parent reply other threads:[~2009-12-02 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 22:56 [patch 4/9] vfs: add lockdep annotation to s_vfs_rename_key for ecryptfs akpm
2009-12-02 0:09 ` Erez Zadok
2009-12-02 0:13 ` Andrew Morton
2009-12-02 0:47 ` Sage Weil
2009-12-02 1:40 ` Ian Kent [this message]
2009-12-02 9:32 ` Miklos Szeredi
2009-12-21 19:44 ` Sage Weil
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=4B15C578.8030503@themaw.net \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--cc=ezk@cs.sunysb.edu \
--cc=kirkland@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=sage@newdream.net \
--cc=tyhicks@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).