From: Sasha Levin <sasha.levin@oracle.com>
To: Josh Boyer <jwboyer@fedoraproject.org>,
Rich Freeman <r-btrfs@thefreemanclan.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Roman Mamedov <rm@romanrm.net>, Chris Mason <clm@fb.com>,
stable <stable@vger.kernel.org>,
Btrfs <linux-btrfs@vger.kernel.org>,
Eric Sandeen <sandeen@redhat.com>
Subject: Re: Please add 9c4f61f01d269815bb7c37be3ede59c5587747c6 to stable
Date: Thu, 23 Apr 2015 14:34:54 -0400 [thread overview]
Message-ID: <55393B4E.30702@oracle.com> (raw)
In-Reply-To: <CA+5PVA6g7Ebez64aJv_d=eB9cj5_vHHyd632bRsr0wY=53KeXg@mail.gmail.com>
On 04/23/2015 02:24 PM, Josh Boyer wrote:
> On Thu, Apr 23, 2015 at 2:16 PM, Rich Freeman
> <r-btrfs@thefreemanclan.net> wrote:
>> > On Mon, Apr 13, 2015 at 12:58 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>>> >> On Mon, Apr 13, 2015 at 07:28:38PM +0500, Roman Mamedov wrote:
>>>> >>> On Thu, 2 Apr 2015 10:17:47 -0400
>>>> >>> Chris Mason <clm@fb.com> wrote:
>>>> >>>
>>>>> >>> > Hi stable friends,
>>>>> >>> >
>>>>> >>> > Can you please backport this one to 3.19.y. It fixes a bug introduced
>>>>> >>> > by:
>>>>> >>> >
>>>>> >>> > 381cf6587f8a8a8e981bc0c1aaaa8859b51dc756, which was tagged for stable
>>>>> >>> > 3.14+
>>>>> >>> >
>>>>> >>> > The symptoms of the bug are deadlocks during log reply after a crash.
>>>>> >>> > The patch wasn't intentionally fixing the deadlock, which is why we
>>>>> >>> > missed it when tagging fixes.
>>>> >>>
>>>> >>> Unfortunately still not fixed (no btrfs-related changes) in 3.14.38 and
>>>> >>> 3.18.11 released today.
>>> >>
>>> >> I have a few hundred stable backports left to sort through, don't worry,
>>> >> this is still in the queue, it's not lost.
>> >
>> > It looks like this still isn't in 3.18.12, though it looks like it is in 3.19.5.
> Sasha is maintaining the 3.18.y stable tree, not Greg. Added to CC.
Um, that commit was shipped back in 3.18.9.
Thanks,
Sasha
next prev parent reply other threads:[~2015-04-23 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 14:17 Please add 9c4f61f01d269815bb7c37be3ede59c5587747c6 to stable Chris Mason
2015-04-06 8:58 ` Luis Henriques
2015-04-13 14:28 ` Roman Mamedov
2015-04-13 16:58 ` Greg KH
2015-04-23 18:16 ` Rich Freeman
2015-04-23 18:24 ` Josh Boyer
2015-04-23 18:34 ` Sasha Levin [this message]
2015-04-23 18:38 ` Sasha Levin
2015-04-23 18:25 ` Greg KH
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=55393B4E.30702@oracle.com \
--to=sasha.levin@oracle.com \
--cc=clm@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=r-btrfs@thefreemanclan.net \
--cc=rm@romanrm.net \
--cc=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).