From: Chris Mason <chris.mason@oracle.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [GIT PULL] Btrfs updates for 2.6.30-rc
Date: Mon, 27 Apr 2009 14:05:55 -0400 [thread overview]
Message-ID: <1240855555.5529.11.camel@think.oraclecorp.com> (raw)
Hello everyone,
The master branch of:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git
Has a few btrfs bug fixes, performance fixes and a few cleanups. The
highlights are some code from Josef Bacik to for metadata block group
preallocation, which will help cut down on the chances of metadata
enospc.
Linus found an acl caching bug that made for many many btree searches
for acls on inodes that didn't have acls, and that is fixed up as well.
Chris Mason (7) commits (+144/-237):
Btrfs: look for acls during btrfs_read_locked_inode (+62/-0)
Btrfs: fix deadlocks and stalls on dead root removal (+6/-0)
Btrfs: fix fallocate deadlock on inode extent lock (+29/-17)
Btrfs: remove unused btrfs_bit_radix slab (+0/-8)
Btrfs: ratelimit IO error printks (+31/-17)
Btrfs: remove #if 0 code (+1/-188)
Btrfs: fix acl caching (+15/-7)
Christoph Hellwig (3) commits (+30/-66):
Btrfs: kill btrfs_cache_create (+28/-43)
Btrfs: don't export symbols (+0/-6)
Btrfs: simplify makefile (+2/-17)
Joel Becker (2) commits (+41/-24):
Btrfs: Fix a trivial warning using max() of u64 vs ULL. (+1/-1)
Btrfs: Fix a bunch of printk() warnings. (+40/-23)
Josef Bacik (1) commits (+42/-2):
Btrfs: try to keep a healthy ratio of metadata vs data block groups
Chris Ball (1) commits (+27/-11):
Btrfs: When shrinking, only update disk size on success
Total: (14) commits
fs/btrfs/Makefile | 19 -----
fs/btrfs/acl.c | 18 +++--
fs/btrfs/ctree.h | 6 +
fs/btrfs/disk-io.c | 93 ++++++++------------------
fs/btrfs/extent-tree.c | 49 +++++++++++---
fs/btrfs/extent_io.c | 81 +----------------------
fs/btrfs/extent_map.c | 17 ----
fs/btrfs/file.c | 89 +------------------------
fs/btrfs/free-space-cache.c | 15 ++--
fs/btrfs/inode-map.c | 2
fs/btrfs/inode.c | 153 ++++++++++++++++++++++++++++++--------------
fs/btrfs/ioctl.c | 9 +-
fs/btrfs/super.c | 27 +++++--
fs/btrfs/transaction.c | 6 +
fs/btrfs/tree-log.c | 2
fs/btrfs/volumes.c | 35 ++++++----
fs/btrfs/volumes.h | 3
17 files changed, 284 insertions(+), 340 deletions(-)
next reply other threads:[~2009-04-27 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 18:05 Chris Mason [this message]
2009-05-08 9:22 ` [GIT PULL] Btrfs updates for 2.6.30-rc Jeff Chua
2009-05-09 1:43 ` Jeff Chua
-- strict thread matches above, loose matches on Subject: below --
2009-05-14 19:19 Chris Mason
2009-05-15 2:13 ` Chris Mason
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=1240855555.5529.11.camel@think.oraclecorp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox