linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: please review recent fixes for file write and fiemap
Date: Wed, 9 Mar 2011 00:06:37 -0600	[thread overview]
Message-ID: <AANLkTimxffcWmYp4rV4MLYUbjRUHwN0cpR-LUcPgix7+@mail.gmail.com> (raw)
In-Reply-To: <1299606753-sup-5310@think>

On Tue, Mar 8, 2011 at 11:58 AM, Chris Mason <chris.mason@oracle.com> w=
rote:
> 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 thin=
g.
> This included looping forever, or pretending pages were up to date wh=
en
> they really were not.
>
> There is also another fiemap fix. Our fiemap was returning overlappin=
g
> extents, which made recent versions of cp copy too many bytes into th=
e
> 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: =A0 Tue Mar 8 11:54:40 2011 -0500
>
> =A0 =A0Btrfs: make sure not to return overlapping extents to fiemap
>
> Please read them, and try to break them ;)
>
> -chris

I applied these three patches as commited to btrfs-unstable, and
re-tested the operations that had been giving me problems (Openmotif
and gcc-4.4.5 building).

They are working good for me.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2011-03-09  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 17:58 please review recent fixes for file write and fiemap Chris Mason
2011-03-09  6:06 ` Mitch Harder [this message]

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=AANLkTimxffcWmYp4rV4MLYUbjRUHwN0cpR-LUcPgix7+@mail.gmail.com \
    --to=mitch.harder@sabayonlinux.org \
    --cc=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).