linux-kernel - Re: early microcode: how to disable at runtime?

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: <20140904154246.GA10884@nazgul.tnic>
Date:	Thu, 4 Sep 2014 17:42:46 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Fenghua Yu <fenghua.yu@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: early microcode: how to disable at runtime?

On Wed, Sep 03, 2014 at 09:43:02AM -0300, Henrique de Moraes Holschuh wrote:
> Half the things you'd usually do when writing kernel code cannot be done
> that early, that's how.  It is not that the code is bad or especially
> fragile (at least not the core or the AMD driver.  The Intel driver is
> convoluted).

Right, it could use some cleaning up.

> You have fixed several such bugs recently, commit ids:
> 75a1ba5b2c529db60ca49626bcaf0bddf4548438,
> 84516098b58e05821780dc0b89abcee434b4dca5,
> 5335ba5cf475369f88db8e6835764efdcad8ab96.

Those were unfortunate because the original patches didn't get tested
enough and got applied. This is not happening again on my watch.

> Yes. It is a stop gap solution, I never claimed it to be anything
> else.
>
> What I did claim is that it is going to be a far more user-friendly
> stop gap than the "boot from rescue media" option.

Ok, we have it now and we can use it if needed. All is good.

-- 
Regards/Gruss,
    Boris.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/