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:   Sun, 11 Jun 2023 00:37:34 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Breno Leitao <leitao@...ian.org>, bp@...en8.de,
        pawan.kumar.gupta@...ux.intel.com, paul@...l-moore.com
Cc:     leit@...a.com, x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpu/bugs: Disable CPU mitigations at compilation time

On Fri, Feb 03 2023 at 04:06, Breno Leitao wrote:
> Right now it is not possible to disable CPU vulnerabilities mitigations
> at build time. Mitigation needs to be disabled passing kernel
> parameters, such as 'mitigations=off'.
>
> Create a new config option (CONFIG_CPU_MITIGATIONS_DEFAULT_OFF) that
> sets the global variable `cpu_mitigations` to OFF, instead of AUTO. This
> allows the creation of kernel binaries that boots with the CPU
> mitigations turned off by default, and does not require dealing kernel
> parameters.

Why? What's the justification

Just because we do not have not enough kernel config items yet, does not
count.

Thanks,

        tglx

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ