From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [GIT PULL] Btrfs update for 2.6.35-rc
Date: Mon, 19 Jul 2010 20:48:06 -0400 [thread overview]
Message-ID: <20100720004806.GE3133@think> (raw)
Hi everyone,
This batch has changes I've been testing in the master branch of the
btrfs-unstable repo
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master
The first deals with the balancing bug that Edward Shishkin found. The
others are bugs that have turned up during the rc.
Chris Mason (1) commits (+111/-18):
Btrfs: fix split_leaf double split corner case
Dan Rosenberg (1) commits (+2/-2):
Btrfs: fix checks in BTRFS_IOC_CLONE_RANGE
Sage Weil (1) commits (+13/-3):
Btrfs: fix CLONE ioctl destination file size expansion to block boundary
Total: (3) commits (+126/-23)
fs/btrfs/ctree.c | 129 ++++++++++++++++++++++++++++++++++++++++++++++--------
fs/btrfs/ioctl.c | 20 ++++++--
2 files changed, 126 insertions(+), 23 deletions(-)
reply other threads:[~2010-07-20 0:48 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=20100720004806.GE3133@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;
as well as URLs for NNTP newsgroup(s).