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]

Date:	Mon, 1 Sep 2014 16:59:21 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Borislav Petkov <bp@...en8.de>, Fenghua Yu <fenghua.yu@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: early microcode: how to disable at runtime?

On Mon, 01 Sep 2014, H. Peter Anvin wrote:
> No, it is worse to rename it and have older kernels behave differently.
> Kernel options are basically super obscure to most people anyway.

Ok, so rename is out, although as long as the rename was accepted for
3.16-stable, it would be just 3.16 and 3.16.1 (and maybe 3.16.2) that would
not have the new name.

Options left are "keep it as is", or "add new and [optionally] deprecate
old".  I can't really tell for sure which one you'd prefer from your
previous answer.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/