xfs
[Top] [All Lists]

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

To: xfs@xxxxxxxxxxx
Subject: [XFS updates] XFS development tree branch, master, updated. v2.6.30-rc4-1256-g7509ee3
From: xfs@xxxxxxxxxxx
Date: Tue, 11 Aug 2009 11:07:02 -0500
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
  7509ee3 xfs: switch to NOFS allocation under i_lock in xfs_attr_rmtval_get
  5a25f1a xfs: switch to NOFS allocation under i_lock in xfs_readlink_bmap
  f56ebd6 xfs: switch to NOFS allocation under i_lock in xfs_attr_rmtval_set
  837273b xfs: switch to NOFS allocation under i_lock in 
xfs_buf_associate_memory
  ea78cd5 xfs: switch to NOFS allocation under i_lock in xfs_dir_cilookup_result
  eeb6f67 xfs: switch to NOFS allocation under i_lock in xfs_da_buf_make
  0043dd8 xfs: switch to NOFS allocation under i_lock in xfs_da_state_alloc
  1ec2b8a xfs: switch to NOFS allocation under i_lock in xfs_getbmap
  efe1f30 xfs: avoid memory allocation under m_peraglock in growfs code
      from  a81655ae5a9da16a08ba14637dc6c10217e57492 (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 7509ee34a365c041718d0b676e5ee255b58b5dda
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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@xxxxxx>
    Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
    Signed-off-by: Felix Blyakher <felixb@xxxxxxx>

commit 5a25f1abb26f5ab7c6c72fe0b3807c137ee484bb
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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@xxxxxx>
    Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
    Signed-off-by: Felix Blyakher <felixb@xxxxxxx>

commit f56ebd66df411446030e2cc820554c6ce4ba0836
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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@xxxxxx>
    Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
    Signed-off-by: Felix Blyakher <felixb@xxxxxxx>

commit 837273b8a150a3761467573c5eb477791cf19268
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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@xxxxxx>
    Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
    Signed-off-by: Felix Blyakher <felixb@xxxxxxx>

commit ea78cd5e6b6ebe123641382d5040252d19829332
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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@xxxxxx>
    Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
    Signed-off-by: Felix Blyakher <felixb@xxxxxxx>

commit eeb6f67ba1176a141b6802b2ec8505835482f631
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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@xxxxxx>
    Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
    Signed-off-by: Felix Blyakher <felixb@xxxxxxx>

commit 0043dd88af762d3a9154317d351400b5b941ec8d
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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@xxxxxx>
    Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
    Signed-off-by: Felix Blyakher <felixb@xxxxxxx>

commit 1ec2b8a777d6ac5464a836b3c5520b1a5190194c
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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@xxxxxx>
    Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
    Signed-off-by: Felix Blyakher <felixb@xxxxxxx>

commit efe1f30e8f05a3836dfcf6302774707b3b47193f
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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@xxxxxx>
    Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
    Signed-off-by: Felix Blyakher <felixb@xxxxxxx>

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

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_da_btree.c      |    6 +++---
 fs/xfs/xfs_dir2.c          |    2 +-
 fs/xfs/xfs_fsops.c         |   20 ++++++++++++++------
 fs/xfs/xfs_vnodeops.c      |    4 +++-
 7 files changed, 28 insertions(+), 16 deletions(-)


hooks/post-receive
-- 
XFS development tree

<Prev in Thread] Current Thread [Next in Thread>
  • [XFS updates] XFS development tree branch, master, updated. v2.6.30-rc4-1256-g7509ee3, xfs <=