linux-kernel - Re: [PATCH v2] x86/bugs: Break down mitigations configurations

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:   Wed, 21 Jun 2023 15:52:56 -0700
From:   Breno Leitao <leitao@...ian.org>
To:     Dave Hansen <dave.hansen@...el.com>
Cc:     Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
        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 Wed, Jun 21, 2023 at 03:35:45PM -0700, Dave Hansen wrote:
> On 6/21/23 12:41, Pawan Gupta wrote:
> > Yes, a single series (or a patch) that adds config for each mitigation
> > would be good.
> 
> Do people _really_ want per-mitigation compile-time controls?  That
> seems like kinda a pain.
> 
> I Boris suggested it, but it seems like a _bit_ of overkill to me.
> 
> Would a compile-time option that just defaulted _everything_ to
> mitigations=off behavior work instead?  That way we don't end up with a
> billion new config options.

This is exactly what my original patch proposed. It solves the problem with
a few lines of changes.

https://lore.kernel.org/lkml/20230203120615.1121272-1-leitao@debian.org/