linux-kernel - Re: [PATCH 5.10 60/76] f2fs: fix to do sanity check on last xattr entry in __f2fs

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: <YdQZzAQg4vIQNXc4@eldamar.lan>
Date:   Tue, 4 Jan 2022 10:56:28 +0100
From:   Salvatore Bonaccorso <carnil@...ian.org>
To:     Chao Yu <chao@...nel.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Wenqing Liu <wenqingliu0120@...il.com>,
        Jaegeuk Kim <jaegeuk@...nel.org>
Subject: Re: [PATCH 5.10 60/76] f2fs: fix to do sanity check on last xattr
 entry in __f2fs_setxattr()

Hi,

On Tue, Jan 04, 2022 at 05:29:30PM +0800, Chao Yu wrote:
> On 2022/1/4 5:11, Salvatore Bonaccorso wrote:
> > Hi,
> > 
> > On Mon, Dec 27, 2021 at 04:31:15PM +0100, Greg Kroah-Hartman wrote:
> > > From: Chao Yu <chao@...nel.org>
> > > 
> > > commit 5598b24efaf4892741c798b425d543e4bed357a1 upstream.
> 
> I've no idea.
> 
> I didn't add this line from v1 to v3:
> 
> https://lore.kernel.org/lkml/20211211154059.7173-1-chao@kernel.org/T/
> https://lore.kernel.org/all/20211212071923.2398-1-chao@kernel.org/T/
> https://lore.kernel.org/all/20211212091630.6325-1-chao@kernel.org/T/
> 
> Am I missing anything?

The line is added when a commit from "upstream" is added to the stable
series to identify the upstream commit it is taken from for
cherry-pick (or backport).

Strange so, that the fix is not in mainline actually yet.

Regards,
Salvatore