xfs
[Top] [All Lists]

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

To: xfs@xxxxxxxxxxx
Subject: [XFS updates] XFS development tree branch, for-linus, updated. v3.1-rc1-22-g58d84c4
From: xfs@xxxxxxxxxxx
Date: Thu, 1 Sep 2011 12:40:44 -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-linus has been updated
  58d84c4 xfs: fix ->write_inode return values
  866e4ed xfs: fix xfs_mark_inode_dirty during umount
  242d621 xfs: deprecate the nodelaylog mount option
      from  b6bede3b4cdfbd188557ab50fceec2e91d295edf (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 58d84c4ee0389ddeb86238d5d8359a982c9f7a5b
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Sat Aug 27 05:57:55 2011 +0000

    xfs: fix ->write_inode return values
    
    Currently we always redirty an inode that was attempted to be written out
    synchronously but has been cleaned by an AIL pushed internall, which is
    rather bogus.  Fix that by doing the i_update_core check early on and
    return 0 for it.  Also include async calls for it, as doing any work for
    those is just as pointless.  While we're at it also fix the sign for the
    EIO return in case of a filesystem shutdown, and fix the completely
    non-sensical locking around xfs_log_inode.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>
    (cherry picked from commit 297db93bb74cf687510313eb235a7aec14d67e97)
    
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 866e4ed77448a0c311e1b055eb72ea05423fd799
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Sat Aug 27 05:57:44 2011 +0000

    xfs: fix xfs_mark_inode_dirty during umount
    
    During umount we do not add a dirty inode to the lru and wait for it to
    become clean first, but force writeback of data and metadata with
    I_WILL_FREE set.  Currently there is no way for XFS to detect that the
    inode has been redirtied for metadata operations, as we skip the
    mark_inode_dirty call during teardown.  Fix this by setting i_update_core
    nanually in that case, so that the inode gets flushed during inode reclaim.
    
    Alternatively we could enable calling mark_inode_dirty for inodes in
    I_WILL_FREE state, and let the VFS dirty tracking handle this.  I decided
    against this as we will get better I/O patterns from reclaim compared to
    the synchronous writeout in write_inode_now, and always marking the inode
    dirty in some way from xfs_mark_inode_dirty is a better safetly net in
    either case.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>
    (cherry picked from commit da6742a5a4cc844a9982fdd936ddb537c0747856)
    
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

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

Summary of changes:
 fs/xfs/xfs_iops.c  |   14 +++++++++++---
 fs/xfs/xfs_super.c |   36 +++++++++++-------------------------
 2 files changed, 22 insertions(+), 28 deletions(-)


hooks/post-receive
-- 
XFS development tree

<Prev in Thread] Current Thread [Next in Thread>
  • [XFS updates] XFS development tree branch, for-linus, updated. v3.1-rc1-22-g58d84c4, xfs <=