From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 2.6.31-rc
Date: Fri, 7 Aug 2009 15:01:09 -0400 [thread overview]
Message-ID: <20090807190109.GI17129@think> (raw)
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(-)
reply other threads:[~2009-08-07 19:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090807190109.GI17129@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