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/4 Unionfs updates/fixes/cleanups
Date: Sat, 26 Jan 2008 00:04:58 -0500	[thread overview]
Message-ID: <12013239022656-git-send-email-ezk@cs.sunysb.edu> (raw)


The following is a series of patchsets related to Unionfs.  This is the
fifth set of patchsets resulting from an lkml review of the entire unionfs
code base, in preparation for a merge into mainline.  The most significant
changes here are a few locking related fixes, and a correction to broken
logic which didn't allow writing to the first available writable branch.

These patches were tested (where appropriate) on 2.6.24, MM, 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).  Also tested
with LTP-full and with a continuous parallel kernel compile (while forcing
cache flushing, manipulating lower branches, etc.).  See
http://unionfs.filesystems.org/ to download back-ported 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 (4):
      Unionfs: use first writable branch (fix/cleanup)
      Unionfs: remove unnecessary call to d_iput
      Unionfs: d_parent related locking fixes
      Unionfs: lock_rename related locking fixes

 copyup.c |   16 --
 inode.c  |  395 ++++++++++++++++++++++++---------------------------------------
 rename.c |   16 ++
 union.h  |    4 
 4 files changed, 174 insertions(+), 257 deletions(-)

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

             reply	other threads:[~2008-01-26  5:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  5:04 Erez Zadok [this message]
2008-01-26  5:04 ` [PATCH 1/4] Unionfs: use first writable branch (fix/cleanup) Erez Zadok
2008-01-26  5:05 ` [PATCH 2/4] Unionfs: remove unnecessary call to d_iput Erez Zadok
2008-01-26  5:05 ` [PATCH 3/4] Unionfs: d_parent related locking fixes Erez Zadok
2008-01-26  5:05 ` [PATCH 4/4] Unionfs: lock_rename " Erez Zadok
  -- strict thread matches above, loose matches on Subject: below --
2008-01-10  2:16 [GIT PULL -mm] 0/4 Unionfs updates/fixes/cleanups 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=12013239022656-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).