[XFS updates] XFS development tree branch, master, updated. v2.6.30-rc4-1259-g79dd43b

[xfs at oss.sgi.com]

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, master has been updated
  79dd43b xfs: fix spin_is_locked assert on uni-processor builds
  16715db xfs: check for dinode realtime flag corruption
  583e0e4 use XFS_CORRUPTION_ERROR in xfs_btree_check_sblock
      from  7509ee34a365c041718d0b676e5ee255b58b5dda (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 79dd43bb85d64ba14a781f940c858d7bbe8c9a6d
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 16715dbe64ccac265010ab8b60848d212d002521
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 583e0e41ee29478e2147aeffeb772657f8db767a
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>

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

Summary of changes:
 fs/xfs/xfs_btree.c |    4 ++--
 fs/xfs/xfs_inode.c |   10 ++++++++++
 fs/xfs/xfs_log.c   |    2 +-
 3 files changed, 13 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
XFS development tree