[GIT PULL] XFS update for 2.6.25-rc5

[Lachlan McIlroy]

Please pull from the for-linus branch:
    git pull git://oss.sgi.com:8090/xfs/xfs-2.6.git for-linus

This will update the following files:

 fs/xfs/xfs_iget.c      |    1 +
 fs/xfs/xfs_trans_ail.c |   17 ++++++++++-------
 2 files changed, 11 insertions(+), 7 deletions(-)

through these commits:

commit 72772a3b5b158cddcfbbff3ef13b26b03a905158
Author: David Chinner <dgc@xxxxxxx>
Date:   Thu Mar 6 13:49:43 2008 +1100

    [XFS] fix inode leak in xfs_iget_core()
    
    If the radix_tree_preload() fails, we need to destroy the inode we just
    read in before trying again. This could leak xfs_vnode structures when
    there is memory pressure. Noticed by Christoph Hellwig.
    
    SGI-PV: 977823
    SGI-Modid: xfs-linux-melb:xfs-kern:30606a
    
    Signed-off-by: David Chinner <dgc@xxxxxxx>
    Signed-off-by: Lachlan McIlroy <lachlan@xxxxxxx>
    Signed-off-by: Christoph Hellwig <hch@xxxxxxxxxxxxx>

commit 92d9cd1059f80b9c89dee191ffb88b0872e6a7ae
Author: David Chinner <dgc@xxxxxxx>
Date:   Thu Mar 6 13:45:10 2008 +1100

    [XFS] 977545 977545 977545 977545 977545 977545 xfsaild causing too many
    wakeups
    
    Idle state is not being detected properly by the xfsaild push code. The
    current idle state is detected by an empty list which may never happen
    with mostly idle filesystem or one using lazy superblock counters. A
    single dirty item in the list that exists beyond the push target can
    result repeated looping attempting to push up to the target because it
    fails to check if the push target has been acheived or not.
    
    Fix by considering a dirty list with everything past the target as an idle
    state and set the timeout appropriately.
    
    SGI-PV: 977545
    SGI-Modid: xfs-linux-melb:xfs-kern:30532a
    
    Signed-off-by: David Chinner <dgc@xxxxxxx>
    Signed-off-by: Christoph Hellwig <hch@xxxxxxxxxxxxx>
    Signed-off-by: Lachlan McIlroy <lachlan@xxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/