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] 00/12 Unionfs updates/fixes/cleanups
Date: Fri, 25 Apr 2008 18:18:56 -0400	[thread overview]
Message-ID: <12091619483888-git-send-email-ezk@cs.sunysb.edu> (raw)


The following is a series of patchsets related to Unionfs.  It includes
fixes to a few races discovered since moving to vm_ops->fault, and one small
optimiztion (skip copyup for when a file is opened for writing but no
writing takes place).

These patches were tested (where appropriate) on v2.6.25-4569-gb69d398, MM
(mmotm 2008-04-19-01-17), as well as the backports to
2.6.{25,24,23,22,21,20,19,18,9} on ext2/3/4, xfs (limited testing -- xfs was
oopsing a lot), reiserfs, nfs2/3/4, jffs2, ramfs, tmpfs, cramfs, and
squashfs (where available).  Also tested with LTP-full-20080229 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 (12):
      Unionfs: minor code cleanups
      Unionfs: prevent races in unionfs_fault
      Unionfs: copy lower times in fsync/fasync only when needed
      Unionfs: lock inode around calls to notify_change()
      Unionfs: stop as soon as first writeable branch is found
      Unionfs: don't dereference dentry without lower branches in d_release
      Unionfs: set append offset correctly for copied-up files
      Unionfs: copyup only if file is being written to
      Unionfs: reorganize file_revalidate for un/locking callers
      Unionfs: maintain one-open-file invariant for non-directories
      Unionfs: set lower file to NULL in file_release
      Unionfs: lock parent dentry branch config in write

 commonfops.c |  248 ++++++++++++++++++++++++++++++++++++++---------------------
 copyup.c     |    2 
 dentry.c     |    4 
 file.c       |   32 +++----
 inode.c      |   43 ++++------
 mmap.c       |   21 +++-
 union.h      |    2 
 7 files changed, 216 insertions(+), 136 deletions(-)

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

             reply	other threads:[~2008-04-25 22:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25 22:18 Erez Zadok [this message]
2008-04-25 22:18 ` [PATCH 01/12] Unionfs: minor code cleanups Erez Zadok
2008-04-25 22:18 ` [PATCH 02/12] Unionfs: prevent races in unionfs_fault Erez Zadok
2008-04-25 22:18 ` [PATCH 03/12] Unionfs: copy lower times in fsync/fasync only when needed Erez Zadok
2008-04-25 22:19 ` [PATCH 04/12] Unionfs: lock inode around calls to notify_change() Erez Zadok
2008-04-25 22:19 ` [PATCH 05/12] Unionfs: stop as soon as first writeable branch is found Erez Zadok
2008-04-25 22:19 ` [PATCH 06/12] Unionfs: don't dereference dentry without lower branches in d_release Erez Zadok
2008-04-25 22:19 ` [PATCH 07/12] Unionfs: set append offset correctly for copied-up files Erez Zadok
2008-04-25 22:19 ` [PATCH 08/12] Unionfs: copyup only if file is being written to Erez Zadok
2008-04-25 22:19 ` [PATCH 09/12] Unionfs: reorganize file_revalidate for un/locking callers Erez Zadok
2008-04-25 22:19 ` [PATCH 10/12] Unionfs: maintain one-open-file invariant for non-directories Erez Zadok
2008-04-25 22:19 ` [PATCH 11/12] Unionfs: set lower file to NULL in file_release Erez Zadok
2008-04-25 22:19 ` [PATCH 12/12] Unionfs: lock parent dentry branch config in write 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=12091619483888-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).