linux-kernel - [GIT PULL] Btrfs updates for 2.6.30-rc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090514191915.GB4268@think>
Date:	Thu, 14 May 2009 15:19:15 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: [GIT PULL] Btrfs updates for 2.6.30-rc

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(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/