linux-kernel - Re: [PATCH] x86, microcode: Remove unnecessary paravirt

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: <CAHp75Vc+xMSiderkF=kZRrerkjzZrZcSCc-LCSNgztk2F896cw@mail.gmail.com>
Date:	Fri, 19 Feb 2016 12:50:45 +0200
From:	Andy Shevchenko <andy.shevchenko@...il.com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Boris Ostrovsky <boris.ostrovsky@...cle.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	david.vrabel@...rix.com,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	xen-devel@...ts.xenproject.org
Subject: Re: [PATCH] x86, microcode: Remove unnecessary paravirt_enabled check

On Fri, Feb 19, 2016 at 12:46 PM, Borislav Petkov <bp@...en8.de> wrote:
> On Fri, Feb 19, 2016 at 12:33:46PM +0200, Andy Shevchenko wrote:
>> No, the commit 84aba677f009 as of today's linux-next on which I commented.
>
> You commented under the "> A subsequent commit, fbae4ba8c4a3" which confused me
> as to which commit is the culprit.

Yeah, at least now it's clear I suppose.

>> commit 84aba677f009e20185aea322563389ad56e0ef7e
>> Author: Boris Ostrovsky <boris.ostrovsky@...cle.com>
>> Date:   Tue Feb 16 09:43:19 2016 +0100
>>
>>     x86/microcode: Remove unnecessary paravirt_enabled check
>>
>> One more thing: I run this kernel as a second from kexec. It might be
>> related as well. For now I have no possibility to run it as a first
>> kernel.
>
> Well, how exactly are you triggering this? Do you have a splat or some
> other register dump so that I can try to pinpoint this. I'll need more
> info so that I can reproduce it here and debug it.

It stuck at some point during boot. I'm trying to get earlycon or
earlyprintk to show me something...

-- 
With Best Regards,
Andy Shevchenko