xfs
[Top] [All Lists]

[XFS updates] XFS development tree branch, for-next, updated. v3.5-rc1-1

To: xfs@xxxxxxxxxxx
Subject: [XFS updates] XFS development tree branch, for-next, updated. v3.5-rc1-12-g9a8d2fd
From: xfs@xxxxxxxxxxx
Date: Thu, 21 Jun 2012 14:50:39 -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, for-next has been updated
  9a8d2fd xfs: remove xlog_t typedef
  ad223e6 xfs: rename log structure to xlog
  11159a0 xfs: shutdown xfs_sync_worker before the log
  bcf62ab xfs: Fix overallocation in xfs_buf_allocate_memory()
  079da28 xfs: fix allocbt cursor leak in xfs_alloc_ag_vextent_near
  76e8f13 xfs: check for stale inode before acquiring iflock on push
      from  51c84223af604ce2d00d0416c30a38c50aed00bd (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 9a8d2fdbb47aaa1eaa136b89da5e5e6b60015c78
Author: Mark Tinguely <tinguely@xxxxxxx>
Date:   Thu Jun 14 09:22:16 2012 -0500

    xfs: remove xlog_t typedef
    
    Remove the xlog_t type definitions.
    
    Signed-off-by: Mark Tinguely <tinguely@xxxxxxx>
    Reviewed-by: Christoph Hellwig <hch@xxxxxx>
    Signed-off-by: Ben Myers <bpm@xxxxxxx>

commit ad223e6030be017470e46f153de27a43979759e0
Author: Mark Tinguely <tinguely@xxxxxxx>
Date:   Thu Jun 14 09:22:15 2012 -0500

    xfs: rename log structure to xlog
    
    Rename the XFS log structure to xlog to help crash distinquish it from the
    other logs in Linux.
    
    Signed-off-by: Mark Tinguely <tinguely@xxxxxxx>
    Reviewed-by: Christoph Hellwig <hch@xxxxxx>
    Signed-off-by: Ben Myers <bpm@xxxxxxx>

commit 11159a0500c1eb7a8a2de37b7dceb53373c75350
Author: Ben Myers <bpm@xxxxxxx>
Date:   Fri May 25 15:45:36 2012 -0500

    xfs: shutdown xfs_sync_worker before the log
    
    Revert commit 1307bbd, which uses the s_umount semaphore to provide
    exclusion between xfs_sync_worker and unmount, in favor of shutting down
    the sync worker before freeing the log in xfs_log_unmount.  This is a
    cleaner way of resolving the race between xfs_sync_worker and unmount
    than using s_umount.
    
    Signed-off-by: Ben Myers <bpm@xxxxxxx>
    Reviewed-by: Mark Tinguely <tinguely@xxxxxxx>
    Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>

commit bcf62ab64d1ba257dd9d4283a077a7219a05073a
Author: Jan Kara <jack@xxxxxxx>
Date:   Wed Jun 6 00:32:26 2012 +0200

    xfs: Fix overallocation in xfs_buf_allocate_memory()
    
    Commit de1cbee which removed b_file_offset in favor of b_bn introduced a bug
    causing xfs_buf_allocate_memory() to overestimate the number of necessary
    pages. The problem is that xfs_buf_alloc() sets b_bn to -1 and thus 
effectively
    every buffer is straddling a page boundary which causes
    xfs_buf_allocate_memory() to allocate two pages and use vmalloc() for access
    which is unnecessary.
    
    Dave says xfs_buf_alloc() doesn't need to set b_bn to -1 anymore since the
    buffer is inserted into the cache only after being fully initialized now.
    So just make xfs_buf_alloc() fill in proper block number from the beginning.
    
    CC: David Chinner <dchinner@xxxxxxxxxx>
    Signed-off-by: Jan Kara <jack@xxxxxxx>
    Reviewed-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
    Signed-off-by: Ben Myers <bpm@xxxxxxx>

commit 079da28c64ebeca357adae77aea3ae7160e45d98
Author: Dave Chinner <dchinner@xxxxxxxxxx>
Date:   Tue Jun 12 14:20:26 2012 +1000

    xfs: fix allocbt cursor leak in xfs_alloc_ag_vextent_near
    
    When we fail to find an matching extent near the requested extent
    specification during a left-right distance search in
    xfs_alloc_ag_vextent_near, we fail to free the original cursor that
    we used to look up the XFS_BTNUM_CNT tree and hence leak it.
    
    Reported-by: Chris J Arges <chris.j.arges@xxxxxxxxxxxxx>
    Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx>
    Reviewed-by: Christoph Hellwig <hch@xxxxxx>
    Signed-off-by: Ben Myers <bpm@xxxxxxx>

commit 76e8f1386673b864cfca3c24c4d5814740e76465
Author: Brian Foster <bfoster@xxxxxxxxxx>
Date:   Mon Jun 11 10:39:43 2012 -0400

    xfs: check for stale inode before acquiring iflock on push
    
    An inode in the AIL can be flush locked and marked stale if
    a cluster free transaction occurs at the right time. The
    inode item is then marked as flushing, which causes xfsaild
    to spin and leaves the filesystem stalled. This is
    reproduced by running xfstests 273 in a loop for an
    extended period of time.
    
    Check for stale inodes before the flush lock. This marks
    the inode as pinned, leads to a log flush and allows the
    filesystem to proceed.
    
    Signed-off-by: Brian Foster <bfoster@xxxxxxxxxx>
    Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
    Reviewed-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Mark Tinguely <tinguely@xxxxxxx>
    Signed-off-by: Ben Myers <bpm@xxxxxxx>

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

Summary of changes:
 fs/xfs/xfs_alloc.c       |    1 +
 fs/xfs/xfs_buf.c         |   16 +--
 fs/xfs/xfs_inode_item.c  |   17 ++-
 fs/xfs/xfs_log.c         |  296 ++++++++++++++++++++++++++++------------------
 fs/xfs/xfs_log_cil.c     |   22 ++--
 fs/xfs/xfs_log_priv.h    |   62 +++++++---
 fs/xfs/xfs_log_recover.c |  178 +++++++++++++++-------------
 fs/xfs/xfs_mount.h       |    4 +-
 fs/xfs/xfs_sync.c        |   32 ++---
 fs/xfs/xfs_trace.h       |   18 +--
 10 files changed, 365 insertions(+), 281 deletions(-)


hooks/post-receive
-- 
XFS development tree

<Prev in Thread] Current Thread [Next in Thread>
  • [XFS updates] XFS development tree branch, for-next, updated. v3.5-rc1-12-g9a8d2fd, xfs <=