linux-kernel - [GIT PULL] Btrfs fixes for 2.6.31-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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 7 Aug 2009 15:01:09 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [GIT PULL] Btrfs fixes for 2.6.31-rc

Hello everyone,

Linus, please pull these from the master branch of:

git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git

These are relatively small bug fixes, including two fixes for 
tree-log recovery on mount (one oops and one infinite loop).

Bartlomiej Zolnierkiewicz (1) commits (+1/-2):
    Btrfs: remove superfluous NULL pointer check in btrfs_rename()

Chris Mason (1) commits (+17/-4):
    Btrfs: make sure the async caching thread advances the key

Josef Bacik (1) commits (+64/-9):
    Btrfs: fix btrfs_remove_from_free_space corner case

Julia Lawall (1) commits (+3/-3):
    Btrfs: correct error-handling zlib error handling

Yan Zheng (1) commits (+7/-2):
    Btrfs: fix balancing oops when invalidate_inode_pages2 returns EBUSY

Total: (5) commits

 fs/btrfs/extent-tree.c      |   21 ++++++++++--
 fs/btrfs/free-space-cache.c |   73 ++++++++++++++++++++++++++++++++++++++------
 fs/btrfs/inode.c            |    3 -
 fs/btrfs/relocation.c       |    9 ++++-
 fs/btrfs/zlib.c             |    6 +--
 5 files changed, 92 insertions(+), 20 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/