linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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/8 Unionfs updates/cleanups/fixes
Date: Fri,  2 Nov 2007 21:22:41 -0400	[thread overview]
Message-ID: <11940529692937-git-send-email-ezk@cs.sunysb.edu> (raw)


The following is a series of patches related to Unionfs.  The main change
here is that we dropped ->sync_page and rewritten ->writepage.

These patches were tested (where appropriate) on Linus's 2.6.24 latest code
(as of v2.6.24-rc1-521-g54866f0), 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:

Erez Zadok (8):
      Unionfs: delete whiteouts in sticky directories
      Unionfs: cleanup permission checking code
      Unionfs: update usage.txt documentation
      Unionfs: mmap updates
      Unionfs: avoid a deadlock during branch-management on a pivot_root'ed union
      Unionfs: don't bother validating inode if it has no lower branches
      Unionfs: don't printk an error if it's due to common copyup
      Unionfs/VFS: no need to export 2 symbols in security/security.c

 Documentation/filesystems/unionfs/usage.txt |   17 +++
 fs/unionfs/commonfops.c                     |    4 
 fs/unionfs/debug.c                          |    6 +
 fs/unionfs/inode.c                          |   96 ++++++-----------
 fs/unionfs/mmap.c                           |  156 ++++++++++------------------
 fs/unionfs/rename.c                         |    2 
 fs/unionfs/subr.c                           |    8 +
 fs/unionfs/union.h                          |   39 +++++--
 security/security.c                         |    2 
 9 files changed, 158 insertions(+), 172 deletions(-)

---
Erez Zadok
ezk@cs.sunysb.edu

             reply	other threads:[~2007-11-03  1:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03  1:22 Erez Zadok [this message]
2007-11-03  1:22 ` [PATCH 1/8] Unionfs: delete whiteouts in sticky directories Erez Zadok
2007-11-03  1:22 ` [PATCH 2/8] Unionfs: cleanup permission checking code Erez Zadok
2007-11-03  1:22 ` [PATCH 3/8] Unionfs: update usage.txt documentation Erez Zadok
2007-11-03  1:22 ` [PATCH 4/8] Unionfs: mmap updates Erez Zadok
2007-11-03  1:22 ` [PATCH 5/8] Unionfs: avoid a deadlock during branch-management on a pivot_root'ed union Erez Zadok
2007-11-03  1:22 ` [PATCH 6/8] Unionfs: don't bother validating inode if it has no lower branches Erez Zadok
2007-11-03  1:22 ` [PATCH 7/8] Unionfs: don't printk an error if it's due to common copyup Erez Zadok
2007-11-03  1:22 ` [PATCH 8/8] Unionfs/VFS: no need to export 2 symbols in security/security.c 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=11940529692937-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).