linux-kernel - RE: [PATCH -v2 0/5] Further sanitize INTEL

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]

Date:   Tue, 27 Aug 2019 20:44:23 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Peter Zijlstra <peterz@...radead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     "x86@...nel.org" <x86@...nel.org>,
        "Hansen, Dave" <dave.hansen@...el.com>,
        Borislav Petkov <bp@...en8.de>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: RE: [PATCH -v2 0/5] Further sanitize INTEL_FAM6 naming

> I'm reposting because the version Ingo applied and partially fixed up still
> generates build bot failure.

Looks like this version gets them all. I built my standard config, allmodconfig and allyesconfig.

Reviewed-by: Tony Luck <tony.luck@...el.com>

What happens next? Will Ingo back out the previous set & his partial fixup and replace
with this series?  Or just slap one extra patch on top of what is already in tip?

First option changes a TIP branch

Second option leaves some bisection breakage in the history.

-Tony