From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: [GIT PULL] Btrfs updates for 2.6.32-rc
Date: Thu, 1 Oct 2009 20:30:52 -0400 [thread overview]
Message-ID: <20091002003052.GA5720@think> (raw)
Hello everyone,
I've prepared the for-linus branch of the btrfs-unstable tree for
pulling:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git for-linus
The master branch has the same changes against 2.6.31, minus a cleanup
from Christoph that is 2.6.32-rc specific.
The big part of this pull request is Josef Bacik's ENOSPC support. He
has added enough tracking to reserve room ahead of time for the metadata
required to meet all the delayed allocations we do, and gotten rid of
the half solutions that were in place before.
We already have small updates planned, and the code doesn't yet make
sure that btrfs-vol -b or device shrinking do the proper reservation to
avoid oopsen. But, it is working nicely and I'd like to get it out for
broader use.
Another change that may get noticed is that Btrfs now uses
CONFIG_BTRFS_POSIX_ACL for testing to see if it should do acls. There
has been some confusion around this and it is more consistent with the
other filesystems. So, if you had acls please make sure you've got the
btrfs posix acl config on.
Chris Ball (2) commits (+7/-5):
Btrfs: Fix setting umask when POSIX ACLs are not enabled (+2/-0)
Btrfs: Use CONFIG_BTRFS_POSIX_ACL to enable ACL code (+5/-5)
Chris Mason (1) commits (+17/-8):
Btrfs: take i_mutex before generic_write_checks
Christoph Hellwig (2) commits (+13/-103):
Btrfs: fix arguments to btrfs_wait_on_page_writeback_range (+3/-1)
Btrfs: remove duplicates of filemap_ helpers (+10/-102)
Josef Bacik (2) commits (+689/-115):
Btrfs: proper -ENOSPC handling (+678/-115)
Btrfs: fix data space leak fix (+11/-0)
Julia Lawall (1) commits (+3/-1):
Btrfs: introduce missing kfree
Sage Weil (2) commits (+23/-20):
Btrfs: fix deadlock with free space handling and user transactions (+1/-1)
Btrfs: fix error cases for ioctl transactions (+22/-19)
Total: (10) commits
fs/btrfs/acl.c | 6
fs/btrfs/btrfs_inode.h | 8
fs/btrfs/ctree.h | 25 ++-
fs/btrfs/disk-io.c | 16 -
fs/btrfs/extent-tree.c | 391 +++++++++++++++++++++++++++++++++++++++++-------
fs/btrfs/extent_io.c | 92 ++++++++---
fs/btrfs/extent_io.h | 13 +
fs/btrfs/file.c | 41 +++--
fs/btrfs/inode.c | 235 +++++++++++++++++++++++++---
fs/btrfs/ioctl.c | 62 +++++--
fs/btrfs/ordered-data.c | 93 -----------
fs/btrfs/ordered-data.h | 4
fs/btrfs/super.c | 2
fs/btrfs/transaction.c | 10 +
fs/btrfs/volumes.c | 4
fs/btrfs/xattr.c | 2
16 files changed, 752 insertions(+), 252 deletions(-)
next reply other threads:[~2009-10-02 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 0:30 Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-09 17:29 [GIT PULL] Btrfs updates for 2.6.32-rc Chris Mason
2009-11-11 21:25 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=20091002003052.GA5720@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox