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: <20230621001327.qdyebewnx7r5aiy3@desk>
Date:   Tue, 20 Jun 2023 17:13:27 -0700
From:   Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
To:     Breno Leitao <leitao@...ian.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Josh Poimboeuf <jpoimboe@...nel.org>, leit@...com,
        "open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)" 
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] x86/bugs: Break down mitigations configurations

On Fri, Jun 16, 2023 at 09:48:50AM -0700, Breno Leitao wrote:
> There is no way to disable MDS, TAA, MMIO Stale data mitigation today at
> compilation time. These mitigations are enabled even if
> CONFIG_SPECULATION_MITIGATIONS is unset.
> 
> Create a new KCONFIG option for each mitigation under
> CONFIG_SPECULATION_MITIGATIONS that allows these
> mitigations to be disabled by default at compilation time.

I don't think all mitigations are still controllable at build-time e.g.
spectre_v2 eIBRS mitigation will still be deployed irrespective of the
config.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ