From: Josef Bacik <jbacik@fb.com>
To: Filipe David Borba Manana <fdmanana@gmail.com>, <xfs@oss.sgi.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] xfstests: add test for btrfs incremental send data corruption
Date: Tue, 28 Jan 2014 08:56:23 -0500 [thread overview]
Message-ID: <52E7B707.4070707@fb.com> (raw)
In-Reply-To: <1390873242-8723-1-git-send-email-fdmanana@gmail.com>
On 01/27/2014 08:40 PM, Filipe David Borba Manana wrote:
> Btrfs incremental send had an issue where it would detect a non-existent
> file hole and then overwrite the file section that hole covers with zeroes,
> overriding file data that it shouldn't.
>
> The respective btrfs kernel patch that fixed this issue is titled:
>
> Btrfs: fix send file hole detection leading to data corruption
> (https://patchwork.kernel.org/patch/3544831/)
>
> Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
>
Thanks for this
Reviewed-by: Josef Bacik <jbacik@fb.com>
Josef
prev parent reply other threads:[~2014-01-28 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 1:40 [PATCH] xfstests: add test for btrfs incremental send data corruption Filipe David Borba Manana
2014-01-28 13:56 ` Josef Bacik [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=52E7B707.4070707@fb.com \
--to=jbacik@fb.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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).