[XFS updates] XFS development tree branch, master, updated. v2.6.28-rc3-13684-gb796313

[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
  b796313 xfs: only issues a cache flush on unmount if barriers are enabled
  ed93ec3 xfs: prevent lockdep false positive in xfs_iget_cache_miss
  e8fa6b4 xfs: prevent kernel crash due to corrupted inode log format
  27e88bf Revert "[XFS] remove old vmap cache"
  7fdf582 Revert "[XFS] use scalable vmap API"
      from  3a011a171906a3a51a43bb860fb7c66a64cab140 (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 b79631330a653f568a2ac4eb4a32474c80e3fe77
Author: Christoph Hellwig <hch at infradead.org>
Date:   Tue Mar 3 14:48:37 2009 -0500

    xfs: only issues a cache flush on unmount if barriers are enabled
    
    Currently we unconditionally issue a flush from xfs_free_buftarg, but
    since 2.6.29-rc1 this gives a warning in the style of
    
    	end_request: I/O error, dev vdb, sector 0
    
    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reviewed-by: Eric Sandeen <sandeen at sandeen.net>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit ed93ec3907f063268ced18728d0653f6199d100c
Author: Christoph Hellwig <hch at infradead.org>
Date:   Tue Mar 3 14:48:35 2009 -0500

    xfs: prevent lockdep false positive in xfs_iget_cache_miss
    
    The inode can't be locked by anyone else as we just created it a few
    lines above and it's not been added to any lookup data structure yet.
    
    So use a trylock that must succeed to get around the lockdep warnings.
    
    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reported-by: Alexander Beregalov <a.beregalov at gmail.com>
    Reviewed-by: Eric Sandeen <sandeen at sandeen.net>
    Reviewed-by: Felix Blyakher <felixb at sgi.com>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

commit e8fa6b483feebd23ded5eb01afd7a6e82b6078c6
Author: Christoph Hellwig <hch at infradead.org>
Date:   Tue Mar 3 14:48:36 2009 -0500

    xfs: prevent kernel crash due to corrupted inode log format
    
    Andras Korn reported an oops on log replay causes by a corrupted
    xfs_inode_log_format_t passing a 0 size to kmem_zalloc.  This patch handles
    to small or too large numbers of log regions gracefully by rejecting the
    log replay with a useful error message.
    
    Signed-off-by: Christoph Hellwig <hch at lst.de>
    Reported-by: Andras Korn <korn-sgi.com at chardonnay.math.bme.hu>
    Reviewed-by: Eric Sandeen <sandeen at sandeen.net>
    Signed-off-by: Felix Blyakher <felixb at sgi.com>

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

Summary of changes:
 fs/xfs/linux-2.6/xfs_buf.c   |   12 ++++++++++--
 fs/xfs/linux-2.6/xfs_buf.h   |    2 +-
 fs/xfs/linux-2.6/xfs_super.c |   10 +++++-----
 fs/xfs/xfs_iget.c            |   15 ++++++++++-----
 fs/xfs/xfs_log_recover.c     |   17 +++++++++++++----
 5 files changed, 39 insertions(+), 17 deletions(-)


hooks/post-receive
-- 
XFS development tree