From: Chris Mason <clm@fb.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Filipe Manana <fdmanana@suse.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs for stable (mostly 3.17)
Date: Tue, 21 Oct 2014 15:19:09 -0400 [thread overview]
Message-ID: <1413919149.13632.0@mail.thefacebook.com> (raw)
In-Reply-To: <20141020221252.GA2101@kroah.com>
On Mon, Oct 20, 2014 at 6:12 PM, Greg KH <gregkh@linuxfoundation.org>
wrote:
> On Mon, Oct 20, 2014 at 01:22:22PM +0100, Filipe Manana wrote:
>
>> May I suggest porting the following commit to 3.14 too?
>>
>>
>> https://urldefense.proofpoint.com/v1/url?u=https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id%3D766b5e5ae78dd04a93a275690a49e23d7dcb1f39&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=4HB2GrskctbPsSOzamEf9hTilGJUhvqoPLn0LWCzaTI%3D%0A&s=c55d2716c1968c22c220de980059a704c31aa637a7036e25909da9cc960bd0f4
>>
>> It fixes a data corruption issue for an incremental send.
>> Particularly
>> important, IMHO, as the corruption happens silently (no errors
>> returned
>> to user space nor any sort of warnings/errors in syslog, etc). It
>> affects only 3.14, and the change applies cleanly on 3.14.22.
>
> Chris, any objection for me taking this?
On vacation, sorry for the lag. Please do take this one too. Thanks
Filipe.
-chris
next prev parent reply other threads:[~2014-10-21 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 10:01 [GIT PULL] Btrfs for stable (mostly 3.17) Chris Mason
2014-10-19 19:55 ` Greg KH
2014-10-19 23:13 ` Greg KH
2014-10-20 12:22 ` Filipe Manana
2014-10-20 22:12 ` Greg KH
2014-10-21 19:19 ` Chris Mason [this message]
2014-10-22 6:23 ` Greg KH
2014-10-20 16:09 ` Chris Mason
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=1413919149.13632.0@mail.thefacebook.com \
--to=clm@fb.com \
--cc=fdmanana@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@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