linux-kernel - Re: [tip:x86/cpu 4/4] Warning: Kernel ABI header at 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at 'arch/x86/include/asm/cpufeatures.h': 111< /* free ( 3*32+29) */

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 for Android: free password hash cracker in your pocket

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

Message-ID: <YLlIsS1brAdNyG4K@zn.tnic>
Date:   Thu, 3 Jun 2021 23:25:05 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:     Borislav Petkov <bp@...e.de>,
        kernel test robot <rong.a.chen@...el.com>,
        Andrew Cooper <andrew.cooper3@...rix.com>,
        kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org,
        x86@...nel.org, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [tip:x86/cpu 4/4] Warning: Kernel ABI header at
 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at
 'arch/x86/include/asm/cpufeatures.h':  111< /* free                                    (
 3*32+29) */

On Wed, Jun 02, 2021 at 12:35:44PM -0300, Arnaldo Carvalho de Melo wrote:
> ... 
> will build in older systems where things added to the updated copy of
> the kernel headers isn't present, so trying to update the file and then
> rebuild perf, only warning me if it doesn't build would give me an early
> warning about things that are breaking and that I should look sooner
> rather than later.
> 
> 	Doing just the diff is not that useful :-)

Lemme see if I understand this correctly: you'd like for the 0day folks
to take those perf-*src-pkg builds, put them on an *old* distro and see
if it builds. Am I close?

And do that with the headers in tools/ which do not have the new changes
and see if they still build?

Or?

Alternatively, we can always go back to keeping the headers in sync with
those in tools/ and f'get about it.

Thoughts?

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette