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:
 <DS0PR12MB9273553AE4096FCCBBB4000E94D62@DS0PR12MB9273.namprd12.prod.outlook.com>
Date: Mon, 10 Mar 2025 20:46:46 +0000
From: "Kaplan, David" <David.Kaplan@....com>
To: Ingo Molnar <mingo@...nel.org>
CC: Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...en8.de>,
	Peter Zijlstra <peterz@...radead.org>, Josh Poimboeuf <jpoimboe@...nel.org>,
	Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, 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>, Brendan
 Jackman <jackmanb@...gle.com>, Derek Manwaring <derekmn@...zon.com>
Subject: RE: [PATCH v4 00/36] Attack vector controls

[AMD Official Use Only - AMD Internal Distribution Only]

> -----Original Message-----
> From: Ingo Molnar <mingo@...nel.org>
> Sent: Monday, March 10, 2025 1:45 PM
> To: Kaplan, David <David.Kaplan@....com>
> Cc: Thomas Gleixner <tglx@...utronix.de>; Borislav Petkov <bp@...en8.de>; Peter
> Zijlstra <peterz@...radead.org>; Josh Poimboeuf <jpoimboe@...nel.org>; Pawan
> Gupta <pawan.kumar.gupta@...ux.intel.com>; Ingo Molnar <mingo@...hat.com>;
> Dave Hansen <dave.hansen@...ux.intel.com>; x86@...nel.org; H . Peter Anvin
> <hpa@...or.com>; linux-kernel@...r.kernel.org; Brendan Jackman
> <jackmanb@...gle.com>; Derek Manwaring <derekmn@...zon.com>
> Subject: Re: [PATCH v4 00/36] Attack vector controls
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> * David Kaplan <david.kaplan@....com> wrote:
>
> > David Kaplan (36):
> >   x86/bugs: Restructure mds mitigation
> >   x86/bugs: Restructure taa mitigation
> >   x86/bugs: Restructure mmio mitigation
> >   x86/bugs: Restructure rfds mitigation
> >   x86/bugs: Remove md_clear_*_mitigation()
> >   x86/bugs: Restructure srbds mitigation
> >   x86/bugs: Restructure gds mitigation
> >   x86/bugs: Restructure spectre_v1 mitigation
> >   x86/bugs: Only allow retbleed=stuff on Intel
> >   x86/bugs: Restructure retbleed mitigation
> >   x86/bugs: Restructure spectre_v2_user mitigation
> >   x86/bugs: Restructure bhi mitigation
> >   x86/bugs: Restructure spectre_v2 mitigation
> >   x86/bugs: Restructure ssb mitigation
> >   x86/bugs: Restructure l1tf mitigation
> >   x86/bugs: Restructure srso mitigation
> >   Documentation/x86: Document the new attack vector controls
> >   cpu: Define attack vectors
> >   x86/Kconfig: Arch attack vector support
> >   x86/bugs: Determine relevant vulnerabilities based on attack vector
> >     controls.
> >   x86/bugs: Add attack vector controls for mds
> >   x86/bugs: Add attack vector controls for taa
> >   x86/bugs: Add attack vector controls for mmio
> >   x86/bugs: Add attack vector controls for rfds
> >   x86/bugs: Add attack vector controls for srbds
> >   x86/bugs: Add attack vector controls for gds
> >   x86/bugs: Add attack vector controls for spectre_v1
> >   x86/bugs: Add attack vector controls for retbleed
> >   x86/bugs: Add attack vector controls for spectre_v2_user
> >   x86/bugs: Add attack vector controls for bhi
> >   x86/bugs: Add attack vector controls for spectre_v2
> >   x86/bugs: Add attack vector controls for l1tf
> >   x86/bugs: Add attack vector controls for srso
> >   x86/pti: Add attack vector controls for pti
> >   x86/bugs: Print enabled attack vectors
> >   cpu: Show attack vectors in sysfs
>
> Just an overall meta comment: could you please capitalize all the acronyms properly
> and consistently in titles, changelogs and the code
> itself:
>
>   s/mds
>    /MDS
>
>   s/srso
>    /SRSO
>
> etc. For single patches we maintainers will routinely fix such issues, but for a 36-
> patch series it's rather tedious ...
>
> Also, please put no periods into titles, and titles should begin with a verb.
>

Ack, will fix.

Thanks --David Kaplan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ