All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs updates for 2.6.30-rc
Date: Thu, 14 May 2009 15:19:15 -0400	[thread overview]
Message-ID: <20090514191915.GB4268@think> (raw)

Hello everyone,

Here's a small btrfs update for the next rc.  The IO failure fixes help
btrfs carry on when metadata reads fail because all copies of a given
block are bad.  There is still a bunch of work to do in that area, but
this a small start that avoids hopeless looping.

Chris Mason (3) commits (+37/-6):
    Btrfs: remove some WARN_ONs in the IO failure path (+0/-3)
    Btrfs: Don't loop forever on metadata IO failures (+36/-3)
    Btrfs: init inode ordered_data_close flag properly (+1/-0)

Li Hong (1) commits (+0/-4):
    Btrfs: remove outdated comment in btrfs_ioctl_resize()

Sankar P (1) commits (+1/-1):
    Btrfs: Spelling fix in btrfs_lookup_first_block_group comments

Sage Weil (1) commits (+2/-2):
    Btrfs: make show_options result match actual option names

Total: (6) commits

 fs/btrfs/ctree.c       |   39 ++++++++++++++++++++++++++++++++++++---
 fs/btrfs/disk-io.c     |    2 --
 fs/btrfs/extent-tree.c |    2 +-
 fs/btrfs/inode.c       |    2 +-
 fs/btrfs/ioctl.c       |    4 ----
 fs/btrfs/super.c       |    4 ++--
 6 files changed, 40 insertions(+), 13 deletions(-)

             reply	other threads:[~2009-05-14 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 19:19 Chris Mason [this message]
2009-05-15  2:13 ` [GIT PULL] Btrfs updates for 2.6.30-rc Chris Mason
  -- strict thread matches above, loose matches on Subject: below --
2009-04-27 18:05 Chris Mason
2009-05-08  9:22 ` Jeff Chua
2009-05-09  1:43   ` Jeff Chua
2009-03-31 20:47 Chris Mason

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=20090514191915.GB4268@think \
    --to=chris.mason@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.