From: Andrew Morton <akpm@linux-foundation.org>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: 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: Tue, 1 Dec 2009 16:13:45 -0800 [thread overview]
Message-ID: <20091201161345.bd3dd2b1.akpm@linux-foundation.org> (raw)
In-Reply-To: <200912020009.nB209Nqx022549@agora.fsl.cs.sunysb.edu>
On Tue, 1 Dec 2009 19:09:23 -0500
Erez Zadok <ezk@cs.sunysb.edu> wrote:
> Any change this patch will be merged soon. It's helpful for other stackable
> file systems as well, and I've verified that it helps my ->rename method
> avoid a lockdep_off/on pair.
>
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
raw-fix-rawctl-compat-ioctls-breakage-on-amd64-and-itanic.patch
vfs-improve-comment-describing-fget_light.patch
ecryptfs-another-lockdep-issue.patch
fs-anon_inodes-implement-dname.patch
fs-remove-unneeded-dcache_unhashed-tricks.patch
fs-improve-remountro-vs-buffercache-coherency.patch
vfs-make-real_lookup-do-dentry-revalidation-with-i_mutex-held.patch
vfs-clean-up-real_lookup.patch
vfs-remove-extraneous-null-d_inode-check-from-do_filp_open.patch
I'll send them out again in a week or so. If nothing happens, I shall go
through them and make some merge decisions myself (be afraid!)
next prev parent reply other threads:[~2009-12-02 0:13 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 [this message]
2009-12-02 0:47 ` Sage Weil
2009-12-02 1:40 ` Ian Kent
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=20091201161345.bd3dd2b1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ezk@cs.sunysb.edu \
--cc=kirkland@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rdreier@cisco.com \
--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 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.