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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <YL+xwYq8LNLY6ePU@kernel.org>
Date:   Tue, 8 Jun 2021 15:06:57 -0300
From:   Arnaldo Carvalho de Melo <acme@...nel.org>
To:     Borislav Petkov <bp@...e.de>
Cc:     Borislav Petkov <bp@...en8.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) */

Em Tue, Jun 08, 2021 at 07:38:26PM +0200, Borislav Petkov escreveu:
> On Tue, Jun 08, 2021 at 02:07:36PM -0300, Arnaldo Carvalho de Melo wrote:
> > Apply the patch, try to build it, it doesn't matter where you build it,
> > only that after applying the patch I want to know if it doersn't build,
> > so that I can look at it earlier than when it gets to my attention by
> > merging upstream, etc.
> 
> I believe if you give the 0day guys a step-by-step what to do, they'll
> probably add it to the lineup. :)

I think I already did it in a another e-mail.
 
> > We're doing it already, Peter wants to help me with it, and I think this
> > has value.
 
> Or, if we start doing that then they don't have to do anything.

Who? Previously its me doing this work, i.e. keeping things in synch.
Actually it is expected that people doing the kernel work don't touch
tools/ wrt adding the copy, there is value in the warning, in looking at
what changed, to see if we should change tooling in some way beyond what
automation in merely making the copy can possibly do.

What has value is checking that the process of addressing the out of
sync warning doesn't break the build, to point to things that will need
human work to get it back to a buildable state.
 
> -- 
> Regards/Gruss,
>     Boris.
> 
> SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

-- 

- Arnaldo