linux-kernel - Re: [PATCH 5.4 fix build id for arm64 with CONFIG

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] [day] [month] [year] [list]

Message-ID: <20230127134017.6uifyex23p54etld@oracle.com>
Date:   Fri, 27 Jan 2023 07:40:17 -0600
From:   Tom Saeger <tom.saeger@...cle.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Sasha Levin <sashal@...nel.org>,
        Naresh Kamboju <naresh.kamboju@...aro.org>,
        John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
        Rich Felker <dalias@...c.org>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Ard Biesheuvel <ardb@...nel.org>,
        Nathan Chancellor <nathan@...nel.org>,
        Dennis Gilmore <dennis@...il.us>,
        Palmer Dabbelt <palmer@...osinc.com>,
        Arnd Bergmann <arnd@...db.de>, stable@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-sh@...r.kernel.org
Subject: Re: [PATCH 5.4 fix build id for arm64 with CONFIG_MODVERSIONS 0/6]

On Fri, Jan 27, 2023 at 08:28:07AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Jan 26, 2023 at 09:08:23PM -0500, Sasha Levin wrote:
> > On Tue, Jan 24, 2023 at 02:14:17PM -0700, Tom Saeger wrote:
> > > Build ID on arm64 is broken if CONFIG_MODVERSIONS=y
> > > on 5.4, 5.10, and 5.15
> > > 
> > > Discussed:
> > > https://lore.kernel.org/all/3df32572ec7016e783d37e185f88495831671f5d.1671143628.git.tom.saeger@oracle.com/
> > > https://lore.kernel.org/all/cover.1670358255.git.tom.saeger@oracle.com/
> > 
> > Queued up, hopefully it makes it this time :) Thanks!
> 
> Dropped from the 5.4 queue as it is not in any newer kernel tree yet,
> sorry.  We can't have a fix that is in only 5.4 but not in a newer
> release, that would mean it would be a regression if someone moves to a
> newer release.
> 
> Tom, please submit patches for _all_ branches, and we will be glad to
> consider them, not just for one old one.
> 
> thanks,
> 
> greg k-h


I was sort of hoping 6/6 would have landed upstream before 
sending v5.10 and v5.15.

I'll send those now.

--Tom