From: Chris Mason <chris.mason@oracle.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
"linux-btrfs" <linux-btrfs@vger.kernel.org>,
"LKML" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Two small btrfs fixes
Date: Tue, 11 Oct 2011 13:27:43 -0400 [thread overview]
Message-ID: <1318353941-sup-6080@shiny> (raw)
Hi Linus,
Li Zefan hit some problems with looping in the btrfs autodefrag mode.
These two commits are in the btrfs-3.0 branch:
git://github.com/chrismason/linux.git btrfs-3.0
Chris Mason (1) commits (+3/-1):
Btrfs: make sure not to defrag extents past i_size
Li Zefan (1) commits (+7/-0):
Btrfs: fix recursive auto-defrag
Total: (2) commits (+10/-1)
fs/btrfs/ioctl.c | 11 ++++++++++-
1 files changed, 10 insertions(+), 1 deletions(-)
reply other threads:[~2011-10-11 17:27 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=1318353941-sup-6080@shiny \
--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