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]

Message-ID: <d9bc78ed-1f05-47db-e916-d4d8bc76634e@intel.com>
Date:   Wed, 21 Jun 2023 15:35:45 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
        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 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.