[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1298666031-sup-6071@think>
Date: Fri, 25 Feb 2011 15:40:58 -0500
From: Chris Mason <chris.mason@...cle.com>
To: "Linus Torvalds" <torvalds@...ux-foundation.org>,
"linux-btrfs" <linux-btrfs@...r.kernel.org>,
"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] Btrfs pull request for 2.6.38
Hi everyone,
Someone just figured out an enospc regression for btrfs, and that patch
isn't ready for this pull request.
But, this pull has some important fixes, especially for btrfs fiemap and
I wanted to make sure it got out the door. Linus, the master branch
of the btrfs unstable tree:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master
Has a nice assortment of fixes for balance crashes, pinned block devices
that can never be reopened, LZO compression oopsen and my favorite -- a
fiemap fix that keeps newer versions of cp from thinking our recently
written files are full of zeros.
In terms of the diffstat, this is almost all fixing btrfs fiemap.
Chris Mason (3) commits (+253/-45):
Btrfs: allow balance to explicitly allocate chunks as it relocates (+21/-1)
Btrfs: put ENOSPC debugging under a mount option (+8/-2)
Btrfs: fix fiemap bugs with delalloc (+224/-42)
Ilya Dryomov (2) commits (+10/-3):
Btrfs: make btrfs_rm_device() fail gracefully (+9/-2)
Btrfs: set FMODE_EXCL in btrfs_device->mode (+1/-1)
Li Zefan (2) commits (+19/-9):
Btrfs: Avoid accessing unmapped kernel address (+14/-7)
Btrfs: Fix BTRFS_IOC_SUBVOL_SETFLAGS ioctl (+5/-2)
Total: (7) commits (+282/-57)
fs/btrfs/ctree.h | 3 +
fs/btrfs/extent-tree.c | 9 +++-
fs/btrfs/extent_io.c | 138 ++++++++++++++++++++++++++++++++++--------------
fs/btrfs/extent_io.h | 2 +-
fs/btrfs/inode.c | 126 +++++++++++++++++++++++++++++++++++++++++++-
fs/btrfs/ioctl.c | 7 ++-
fs/btrfs/lzo.c | 21 +++++---
fs/btrfs/relocation.c | 13 ++++-
fs/btrfs/super.c | 7 ++-
fs/btrfs/volumes.c | 13 ++++-
10 files changed, 282 insertions(+), 57 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/
Powered by blists - more mailing lists