From: Chris Mason <chris.mason@oracle.com>
To: "Linux Btrfs" <linux-btrfs@vger.kernel.org>
Subject: please review recent fixes for file write and fiemap
Date: Tue, 08 Mar 2011 12:58:40 -0500 [thread overview]
Message-ID: <1299606753-sup-5310@think> (raw)
Hi Everyone,
The master branch of the btrfs-unstable tree has three shiny new
commits, which fix some important bugs in file_write and fiemap.
These are not yet pushed to Linus but the plan is to send them out
before the final .38 release.
The commits fix errors in the copy_from_user handling where short
returns or zero returns would make btrfs_file_write do the wrong thing.
This included looping forever, or pretending pages were up to date when
they really were not.
There is also another fiemap fix. Our fiemap was returning overlapping
extents, which made recent versions of cp copy too many bytes into the
destination file.
The top commit is this one (just in case kernel.org hasn't caught up
yet)
commit ea8efc74bd0402b4d5f663d007b4e25fa29ea778
Author: Chris Mason <chris.mason@oracle.com>
Date: Tue Mar 8 11:54:40 2011 -0500
Btrfs: make sure not to return overlapping extents to fiemap
Please read them, and try to break them ;)
-chris
next reply other threads:[~2011-03-08 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 17:58 Chris Mason [this message]
2011-03-09 6:06 ` please review recent fixes for file write and fiemap Mitch Harder
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=1299606753-sup-5310@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.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).