public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: [GIT PULL] xfs: Fixes for 2.6.36-rc3
Date: Wed, 25 Aug 2010 17:28:09 +1000	[thread overview]
Message-ID: <20100825072809.GO31488@dastard> (raw)

Hi Linus,

Can you please pull the XFS and writeback related fixes from the
tree below? There are writeback efficieny fixes, data integrity
fixes, race and sanity fixes for the delayed logging mode, making
the filesystem idle correctly (no more disk writes every 30s),
ensuring df doesn't return negative free inode counts and fixing
a thinko in the untrusted inode validation code.

Thanks,,

Dave.

The following changes since commit 9ee47476d6734c9deb9ae9ab05d963302f6b6150:

  Merge branch 'radix-tree' of git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev (2010-08-22 19:55:14 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev.git 2.6.36-fixes

Christoph Hellwig (1):
      xfs: do not discard page cache data on EAGAIN

Dave Chinner (8):
      xfs: unlock items before allowing the CIL to commit
      xfs: ensure we mark all inodes in a freed cluster XFS_ISTALE
      xfs: fix untrusted inode number lookup
      writeback: write_cache_pages doesn't terminate at nr_to_write <= 0
      xfs: handle negative wbc->nr_to_write during sync writeback
      xfs: dummy transactions should not dirty VFS state
      xfs: Reduce log force overhead for delayed logging
      xfs: don't do memory allocation under the CIL context lock

Stuart Brodsky (1):
      xfs: ensure f_ffree returned by statfs() is non-negative

 fs/xfs/linux-2.6/xfs_aops.c  |   13 ++-
 fs/xfs/linux-2.6/xfs_super.c |    9 +-
 fs/xfs/linux-2.6/xfs_sync.c  |   42 +------
 fs/xfs/xfs_fsops.c           |   31 +++--
 fs/xfs/xfs_fsops.h           |    2 +-
 fs/xfs/xfs_ialloc.c          |   16 ++-
 fs/xfs/xfs_inode.c           |   49 ++++----
 fs/xfs/xfs_log.c             |    7 +-
 fs/xfs/xfs_log_cil.c         |  263 +++++++++++++++++++++++++-----------------
 fs/xfs/xfs_log_priv.h        |   13 ++-
 fs/xfs/xfs_trans.c           |    5 +-
 fs/xfs/xfs_trans_priv.h      |    3 +-
 mm/page-writeback.c          |   26 ++---
 13 files changed, 261 insertions(+), 218 deletions(-)
-- 
Dave Chinner
david@fromorbit.com

                 reply	other threads:[~2010-08-25  7:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100825072809.GO31488@dastard \
    --to=david@fromorbit.com \
    --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