linux-kernel - Re: [PATCH stable-5.4.y] btrfs: fix race between marking inode needs to be logged and log syncing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a0868a8e-7078-94b3-53ee-43d7739e562e@oracle.com>
Date:   Mon, 30 Aug 2021 14:22:21 +0800
From:   Anand Jain <anand.jain@...cle.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        linux-btrfs@...r.kernel.org, Filipe Manana <fdmanana@...e.com>
Subject: Re: [PATCH stable-5.4.y] btrfs: fix race between marking inode needs
 to be logged and log syncing



On 30/08/2021 13:55, Greg KH wrote:
> On Mon, Aug 30, 2021 at 05:28:57AM +0800, Anand Jain wrote:
>> On 29/08/2021 14:55, Greg KH wrote:
>>> On Sat, Aug 28, 2021 at 06:37:28AM +0800, Anand Jain wrote:
>>>> From: Filipe Manana <fdmanana@...e.com>
>>>>
>>>> commit bc0939fcfab0d7efb2ed12896b1af3d819954a14 upstream.
>>>
>>> 5.10 also needs this, can you provide a working backport for that as
>>> well so that no one would get a regression if they moved to a newer
>>> kernel release?  Then we could take this patch.
>>
>> Ok, will do. Why are we keen on stable-5.10.y only, while there are
>> other stable releases in between?
> 
> There are no other stable releases in between that are currently
> supported.  Please see the front page of www.kernel.org for the active
> list.

  Ah. Thx. I was confused by the stable-5.x.y branches in the repo.

-Anand