[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <n65yrom6bgghmdwhuk2gszpltnznx47xftjsbovlo4bufow2en@ux4uuizje6ye>
Date: Mon, 23 Jun 2025 11:35:31 -0700
From: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>
Cc: x86@...nel.org, David Kaplan <david.kaplan@....com>,
linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
Josh Poimboeuf <jpoimboe@...nel.org>, Nikolay Borisov <nik.borisov@...e.com>
Subject: Re: [PATCH v4 0/7] Retbleed fixes
On Sun, Jun 22, 2025 at 06:01:22PM +0200, Borislav Petkov wrote:
> On Wed, Jun 11, 2025 at 10:28:44AM -0700, Pawan Gupta wrote:
> > Pawan Gupta (7):
> > x86/retbleed: Avoid AUTO after the select step
> > x86/retbleed: Simplify the =stuff checks
> > x86/bugs: Avoid warning when overriding return thunk
> > x86/its: Use switch/case to apply mitigation
> > x86/retbleed: Introduce cdt_possible()
> > x86/its: Remove =stuff dependency on retbleed
> > x86/its: Allow stuffing in eIBRS+retpoline mode also
>
> Note that the subject prefixes are "x86/bugs:" not the mitigations themselves.
>
> https://kernel.org/doc/html/latest/process/maintainer-tip.html#patch-subject
Ok.
Do you think also appending the vulnerability name like "x86/bugs/retbleed"
would be useful for someone filtering commits based on vulnerability?
> I've fixed them up.
Thanks.
Powered by blists - more mailing lists