public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: lachlan@sgi.com (Lachlan McIlroy)
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com, akpm@linux-foundation.org
Subject: [GIT PULL] XFS update for 2.6.24-rc6
Date: Tue, 18 Dec 2007 17:59:11 +1100	[thread overview]
Message-ID: <20071218065911.EDC8158C4C0F@chook.melbourne.sgi.com> (raw)

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/linux-2.6/xfs_file.c |    4 ++--
 fs/xfs/xfs_dir2_block.c     |    6 ++----
 fs/xfs/xfs_dir2_leaf.c      |    2 +-
 fs/xfs/xfs_dir2_sf.c        |    9 +++------
 fs/xfs/xfs_inode.c          |    6 ++++--
 5 files changed, 12 insertions(+), 15 deletions(-)

through these commits:

commit 041388b54ed95cd169546bd83bacd08ee32bd7ea
Author: Lachlan McIlroy <lachlan@redback.melbourne.sgi.com>
Date:   Tue Dec 18 16:19:34 2007 +1100

    [XFS] Put the correct offset in dirent d_off
    
    The recent filldir regression fix was not putting the correct d_off in
    each dirent. This was resulting in incorrect cookies being passed to dmapi
    ioctls and the wrong offset appearing in the dirents. readdir was
    unaffected as the filp->f_pos was being updated with the correct offset
    and this was being written into the last dirent in each buffer. Fix the
    XFS code to do the right thing.
    
    SGI-PV: 973746
    SGI-Modid: xfs-linux-melb:xfs-kern:30240a
    
    Signed-off-by: David Chinner <dgc@sgi.com>
    Signed-off-by: Christoph Hellwig <hch@infradead.org>
    Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>

commit c734c79bc397eace039bea406997efa89f879c14
Author: Lachlan McIlroy <lachlan@sgi.com>
Date:   Tue Dec 18 16:17:41 2007 +1100

    [XFS] Don't wait for pending I/Os when purging blocks beyond eof.
    
    On last close of a file we purge blocks beyond eof. The same code is used
    when we truncate the file size down. In this case we need to wait for any
    pending I/Os for dirty pages beyond the new eof. For the last close case
    we are not changing the file size and therefore do not need to wait for
    any I/Os to complete. This fixes a performance bottleneck where writes
    into the page cache and cache flushes can become mutually exclusive.
    
    SGI-PV: 964002
    SGI-Modid: xfs-linux-melb:xfs-kern:30220a
    
    Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
    Signed-off-by: Peter Leckie <pleckie@sgi.com>

             reply	other threads:[~2007-12-18  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18  6:59 Lachlan McIlroy [this message]
2007-12-19  0:41 ` [GIT PULL] XFS update for 2.6.24-rc6 David Chinner
     [not found]   ` <alpine.LFD.0.9999.0712181718430.21557@woody.linux-foundation.org>
2007-12-19  3:12     ` David Chinner
  -- strict thread matches above, loose matches on Subject: below --
2007-12-21  0:42 Lachlan McIlroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071218065911.EDC8158C4C0F@chook.melbourne.sgi.com \
    --to=lachlan@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox