[XFS updates] XFS development tree branch, for-linus, updated. v2.6.30-rc4-4473-ga8914f3

Wed Aug 12 01:08:40 CDT 2009

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "XFS development tree".

The branch, for-linus has been updated
  a8914f3 xfs: fix spin_is_locked assert on uni-processor builds
  b89d420 xfs: check for dinode realtime flag corruption
  e0c222c use XFS_CORRUPTION_ERROR in xfs_btree_check_sblock
  ddd3a14 xfs: switch to NOFS allocation under i_lock in xfs_attr_rmtval_get
  7b02ecb xfs: switch to NOFS allocation under i_lock in xfs_readlink_bmap
  10746e4 xfs: switch to NOFS allocation under i_lock in xfs_attr_rmtval_set
  36fae17 xfs: switch to NOFS allocation under i_lock in xfs_buf_associate_memory
  3f52c2f xfs: switch to NOFS allocation under i_lock in xfs_dir_cilookup_result
  73195ed xfs: switch to NOFS allocation under i_lock in xfs_da_buf_make
  f41d7fb xfs: switch to NOFS allocation under i_lock in xfs_da_state_alloc
  ca35dcd xfs: switch to NOFS allocation under i_lock in xfs_getbmap
  0cc6eee xfs: avoid memory allocation under m_peraglock in growfs code
      from  c8a4051c3731b6db224482218cfd535ab9393ff8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit a8914f3a6d72c97328597a556a99daaf5cc288ae
Author: Christoph Hellwig <hch at lst.de>
Date:   Mon Aug 10 11:32:44 2009 -0300

    xfs: fix spin_is_locked assert on uni-processor builds

    Without SMP or preemption spin_is_locked always returns false,
    so we can't do an assert with it.  Instead use assert_spin_locked,
    which does the right thing on all builds.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Eric Sandeen <sandeen at sandeen.net>
    Reported-by: Johannes Engel <jcnengel at googlemail.com>
    Tested-by: Johannes Engel <jcnengel at googlemail.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit b89d4208de3de442c9025919c4261be0b38e79a4
Author: Christoph Hellwig <hch at lst.de>
Date:   Mon Aug 10 11:32:18 2009 -0300

    xfs: check for dinode realtime flag corruption

    Ramon tested XFS with a modified version of fsfuzzer and hit a NULL
    pointer dereference in __xfs_get_blocks due to the RT device target
    pointer being NULL.

    To fix this reject inode with the realtime bit set on a a filesystem
    without an RT subvolume during inode read.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Eric Sandeen <sandeen at sandeen.net>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Reported-by: Ramon de Carvalho Valle <ramon at risesecurity.org>
    Tested-by: Ramon de Carvalho Valle <ramon at risesecurity.org>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit e0c222c411e22f086e929cd69fdcc89336164ec1
Author: Eric Sandeen <sandeen at sandeen.net>
Date:   Mon Jul 20 10:52:15 2009 -0500

    use XFS_CORRUPTION_ERROR in xfs_btree_check_sblock

    In Red Hat Bug 512552
     - Can't write to XFS mount during raid5 resync

    a user ran into corruption while resyncing a raid, and we failed
    a consistency test, but didn't get much more info; it'd be nice
    to call XFS_CORRUPTION_ERROR here so we can see the buffer
    contents.

    Signed-off-by: Eric Sandeen <sandeen at sandeen.net>
    Reviewed-by: Christoph Hellwig <hch at lst.de>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit ddd3a14e0f030f0f7b900621f67532285b8657ef
Author: Christoph Hellwig <hch at infradead.org>
Date:   Sat Jul 18 18:15:01 2009 -0400

    xfs: switch to NOFS allocation under i_lock in xfs_attr_rmtval_get

    xfs_attr_rmtval_get is always called with i_lock held, but i_lock is taken
    in reclaim context so all allocations under it must avoid recursions into
    the filesystem.

    Reported by the new reclaim context tracing in lockdep.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit 7b02ecb3031b192823bc732ae717febc0a59aa92
Author: Christoph Hellwig <hch at infradead.org>
Date:   Sat Jul 18 18:15:00 2009 -0400

    xfs: switch to NOFS allocation under i_lock in xfs_readlink_bmap

    xfs_readlink_bmap is called with i_lock held, but i_lock is taken in
    reclaim context so all allocations under it must avoid recursions into
    the filesystem.

    Reported by the new reclaim context tracing in lockdep.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit 10746e47e722b5688fcd6eba9fbf9b2e64a248a7
Author: Christoph Hellwig <hch at infradead.org>
Date:   Sat Jul 18 18:14:59 2009 -0400

    xfs: switch to NOFS allocation under i_lock in xfs_attr_rmtval_set

    xfs_attr_rmtval_set is always called with i_lock held, and i_lock is taken
    in reclaim context so all allocations under it must avoid recursions into
    the filesystem.

    Reported by the new reclaim context tracing in lockdep.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit 36fae17a648e0aee5d9560514d08477ef48dc87f
Author: Christoph Hellwig <hch at infradead.org>
Date:   Sat Jul 18 18:14:58 2009 -0400

    xfs: switch to NOFS allocation under i_lock in xfs_buf_associate_memory

    xfs_buf_associate_memory is used for setting up the spare buffer for the
    log wrap case in xlog_sync which can happen under i_lock when called from
    xfs_fsync. The i_lock mutex is taken in reclaim context so all allocations
    under it must avoid recursions into the filesystem.  There are a couple
    more uses of xfs_buf_associate_memory in the log recovery code that are
    also affected by this, but I'd rather keep the code simple than passing on
    a gfp_mask argument.  Longer term we should just stop requiring the memoery
    allocation in xlog_sync by some smaller rework of the buffer layer.

    Reported by the new reclaim context tracing in lockdep.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit 3f52c2f0a07c23771909cc53f2e9451a7f1bf253
Author: Christoph Hellwig <hch at infradead.org>
Date:   Sat Jul 18 18:14:57 2009 -0400

    xfs: switch to NOFS allocation under i_lock in xfs_dir_cilookup_result

    xfs_dir_cilookup_result is always called with i_lock held, but i_lock is taken
    in reclaim context so all allocations under it must avoid recursions into the
    filesystem.

    Reported by the new reclaim context tracing in lockdep.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit 73195ed7864ae4a1fb0bea2ed9df59d19b4fde90
Author: Christoph Hellwig <hch at infradead.org>
Date:   Sat Jul 18 18:14:56 2009 -0400

    xfs: switch to NOFS allocation under i_lock in xfs_da_buf_make

    i_lock is taken in the reclaim context so all allocations under it
    must avoid recursions into the filesystem.

    Reported by the new reclaim context tracing in lockdep.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit f41d7fb9da05b604f8a69fb6cac2a0563c8ede4e
Author: Christoph Hellwig <hch at infradead.org>
Date:   Sat Jul 18 18:14:55 2009 -0400

    xfs: switch to NOFS allocation under i_lock in xfs_da_state_alloc

    xfs_da_state_alloc is always called with i_lock held, but i_lock is taken in
    reclaim context so all allocations under it must avoid recursions into the
    filesystem.

    Reported by the new reclaim context tracing in lockdep.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit ca35dcd6cae7d4a780c484c53f45548c4719f82c
Author: Christoph Hellwig <hch at infradead.org>
Date:   Sat Jul 18 18:14:54 2009 -0400

    xfs: switch to NOFS allocation under i_lock in xfs_getbmap

    xfs_getbmap allocates memory with i_lock held, but i_lock is taken in
    reclaim context so all allocations under it must avoid recursions into
    the filesystem.

    Reported by the new reclaim context tracing in lockdep.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit 0cc6eee130b0c062feec8446d9cecdb17d2cfad3
Author: Christoph Hellwig <hch at infradead.org>
Date:   Sat Jul 18 18:14:53 2009 -0400

    xfs: avoid memory allocation under m_peraglock in growfs code

    Allocate the memory for the larger m_perag array before taking the
    per-AG lock as the per-AG lock can be taken under the i_lock which
    can be taken from reclaim context.

    Reported by the new reclaim context tracing in lockdep.

    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

-----------------------------------------------------------------------

Summary of changes:
 fs/xfs/linux-2.6/xfs_buf.c |    2 +-
 fs/xfs/xfs_attr.c          |    8 +++++---
 fs/xfs/xfs_bmap.c          |    2 +-
 fs/xfs/xfs_btree.c         |    4 ++--
 fs/xfs/xfs_da_btree.c      |    6 +++---
 fs/xfs/xfs_dir2.c          |    2 +-
 fs/xfs/xfs_fsops.c         |   20 ++++++++++++++------
 fs/xfs/xfs_inode.c         |   10 ++++++++++
 fs/xfs/xfs_log.c           |    2 +-
 fs/xfs/xfs_vnodeops.c      |    4 +++-
 10 files changed, 41 insertions(+), 19 deletions(-)

hooks/post-receive
-- 
XFS development tree