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]

Message-ID: <20190828125902.GP2386@hirez.programming.kicks-ass.net>
Date:   Wed, 28 Aug 2019 14:59:02 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     "Luck, Tony" <tony.luck@...el.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "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

On Wed, Aug 28, 2019 at 11:33:01AM +0200, Peter Zijlstra wrote:
> On Tue, Aug 27, 2019 at 11:51:35PM +0200, Peter Zijlstra wrote:
> > On Tue, Aug 27, 2019 at 08:44:23PM +0000, Luck, Tony wrote:
> > > > 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
> > 
> > This is uncommon, but not unheard of. I'll talk to Ingo and Thomas
> > tomorrow to see what would be the best way forward.
> 
> OK, I talked to Thomas and we're going to force update that branch. I've
> pushed it out to my queue.git thing and I'll push it to -tip later
> (hoping the 0day gets a chance to have a go at it, but that thing's been
> soooooo slow recently I'm loath to rely/wait on it).

Done now. tip/x86/cpu should have the shiny new patches in.