[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250226210129.GHZ7-BKYvxN_I3f_B2@fat_crate.local>
Date: Wed, 26 Feb 2025 22:01:29 +0100
From: Borislav Petkov <bp@...en8.de>
To: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
Cc: "Kaplan, David" <David.Kaplan@....com>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>,
"H . Peter Anvin" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 20/35] x86/bugs: Define attack vectors
On Wed, Feb 26, 2025 at 12:14:53PM -0800, Pawan Gupta wrote:
> This is a bit ambiguous, mitigations=off,guest_host could be interpreted as
> disabling guest->host and enabling all others. Using attack vectors with
> both =on and =off seems unnecessary.
No, you'll have
mitigations=[global],[separate_vector(s)]
so global can be "on", "off", "auto" and the separate vector enables only that
specific one.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists