From: Erez Zadok <ezk@cs.sunysb.edu>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
viro@ftp.linux.org.uk, hch@infradead.org
Subject: [GIT PULL -mm] 0/9 Unionfs updates/cleanups/fixes
Date: Sun, 21 Oct 2007 19:51:13 -0400 [thread overview]
Message-ID: <11930106823372-git-send-email-ezk@cs.sunysb.edu> (raw)
The following is a series of patches related to Unionfs. The main change
here is that unionfs now has its own ->writepages method.
These patches were tested (where appropriate) on Linus's 2.6.24 latest code
(as of v2.6.23-6623-g55b70a0), as well as the backports to
2.6.{23,22,21,20,19,18,9} on ext2/3/4, xfs, reiserfs, nfs2/3/4, jffs2,
ramfs, tmpfs, cramfs, and squashfs (where available). See
http://unionfs.filesystems.org/ to download backported unionfs code.
Please pull from the 'master' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/ezk/unionfs.git
to receive the following:
Andrew Morton (2):
Unionfs: security convert lsm into a static interface fix
Unionfs: slab api remove useless ctor parameter and reorder parameters
Erez Zadok (6):
Unionfs: support lower filesystems without writeback capability
Unionfs: don't printk trivial message upon normal rename-copyup
Unionfs: don't bother validating dentry if it has no lower branches
Unionfs: convert a printk to pr_debug in release
Unionfs: remove for_writepages nfs workaround
Unionfs: remove obsolete #define and comment
Jeff Layton (1):
Unionfs: fix unionfs_setattr to handle ATTR_KILL_S*ID
fs/unionfs/debug.c | 4 +++
fs/unionfs/dentry.c | 6 ++--
fs/unionfs/inode.c | 7 +++++
fs/unionfs/mmap.c | 62 +++++++++++++++++------------------------------
fs/unionfs/rename.c | 8 +++---
fs/unionfs/super.c | 4 +--
fs/unionfs/union.h | 1
include/linux/union_fs.h | 3 --
security/security.c | 2 +
9 files changed, 47 insertions(+), 50 deletions(-)
---
Erez Zadok
ezk@cs.sunysb.edu
next reply other threads:[~2007-10-21 23:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 23:51 Erez Zadok [this message]
2007-10-21 23:51 ` [PATCH 1/9] Unionfs: security convert lsm into a static interface fix Erez Zadok
2007-10-22 8:22 ` Christoph Hellwig
2007-10-23 0:48 ` Erez Zadok
2007-10-23 9:07 ` Christoph Hellwig
2007-10-27 23:01 ` Erez Zadok
2007-10-21 23:51 ` [PATCH 2/9] Unionfs: slab api remove useless ctor parameter and reorder parameters Erez Zadok
2007-10-21 23:51 ` [PATCH 3/9] Unionfs: support lower filesystems without writeback capability Erez Zadok
2007-10-21 23:51 ` [PATCH 4/9] Unionfs: don't printk trivial message upon normal rename-copyup Erez Zadok
2007-10-21 23:51 ` [PATCH 5/9] Unionfs: don't bother validating dentry if it has no lower branches Erez Zadok
2007-10-21 23:51 ` [PATCH 6/9] Unionfs: convert a printk to pr_debug in release Erez Zadok
2007-10-21 23:51 ` [PATCH 7/9] Unionfs: remove for_writepages nfs workaround Erez Zadok
2007-10-21 23:51 ` [PATCH 8/9] Unionfs: fix unionfs_setattr to handle ATTR_KILL_S*ID Erez Zadok
2007-10-21 23:51 ` [PATCH 9/9] Unionfs: remove obsolete #define and comment Erez Zadok
-- strict thread matches above, loose matches on Subject: below --
2007-11-13 10:10 [GIT PULL -mm] 0/9 Unionfs updates/cleanups/fixes Erez Zadok
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=11930106823372-git-send-email-ezk@cs.sunysb.edu \
--to=ezk@cs.sunysb.edu \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.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).