From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: "Kaplan, David" <David.Kaplan@amd.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/bugs: Restructure ITS mitigation
Date: Thu, 15 May 2025 15:02:43 -0700 [thread overview]
Message-ID: <20250515220243.fk4z7rifcxdm2e7h@desk> (raw)
In-Reply-To: <LV3PR12MB92655C23DF46F1F3B88139009490A@LV3PR12MB9265.namprd12.prod.outlook.com>
On Thu, May 15, 2025 at 09:15:59PM +0000, Kaplan, David wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> > -----Original Message-----
> > From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> > Sent: Thursday, May 15, 2025 4:12 PM
> > To: Kaplan, David <David.Kaplan@amd.com>
> > Cc: Thomas Gleixner <tglx@linutronix.de>; Borislav Petkov <bp@alien8.de>; Peter
> > Zijlstra <peterz@infradead.org>; Josh Poimboeuf <jpoimboe@kernel.org>; Ingo
> > Molnar <mingo@redhat.com>; Dave Hansen <dave.hansen@linux.intel.com>;
> > x86@kernel.org; H. Peter Anvin <hpa@zytor.com>; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH] x86/bugs: Restructure ITS mitigation
> >
> > Caution: This message originated from an External Source. Use proper caution
> > when opening attachments, clicking links, or responding.
> >
> >
> > On Thu, May 15, 2025 at 08:47:56AM -0500, David Kaplan wrote:
> > ...
> > > +static void __init its_apply_mitigation(void) {
> > > + /* its=stuff forces retbleed stuffing and is enabled there. */
> > > + if (its_mitigation != ITS_MITIGATION_ALIGNED_THUNKS)
> > > + return;
> > > +
> > > + if (!boot_cpu_has(X86_FEATURE_RETPOLINE))
> > > + setup_force_cpu_cap(X86_FEATURE_INDIRECT_THUNK_ITS);
> > > +
> > > + setup_force_cpu_cap(X86_FEATURE_RETHUNK);
> > > + set_return_thunk(its_return_thunk);
> > > +}
> > > +
> > > #undef pr_fmt
> > > #define pr_fmt(fmt) "Spectre V2 : " fmt
> > >
> > >
> > > base-commit: 04bdd560124ec4d02d1d11ee3abc88d51954d7b8
> >
> > I am having trouble applying this patch to upstream and tip/master. I can't seem to
> > find this base-commit in Linus's or tip tree. Please let me know what am I missing?
>
> Hmm. I was working off origin/master on tip. This was the base commit in my git log from this morning:
>
> commit 04bdd560124ec4d02d1d11ee3abc88d51954d7b8 (origin/master, origin/HEAD)
> Merge: 61e94712bb24 e59236b5a09e
> Author: Ingo Molnar <mingo@kernel.org>
> Date: Thu May 15 10:16:23 2025 +0200
>
> Not sure if something happened to it since?
Likely yes. I am getting:
Notice: this object is not reachable from any branch.
when I go to this link:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit?id=04bdd560124ec4d02d1d11ee3abc88d51954d7b8
> Or is there something else I can provide to help?
No, I am able to apply now. Earlier my b4 based script failed because it
couldn't find the base-commit. It works when I am apply manually, sorry to
bother you.
next prev parent reply other threads:[~2025-05-15 22:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 13:47 David Kaplan
2025-05-15 15:16 ` Borislav Petkov
2025-05-15 21:11 ` Pawan Gupta
2025-05-15 21:15 ` Kaplan, David
2025-05-15 22:02 ` Pawan Gupta [this message]
2025-05-16 14:56 ` Borislav Petkov
2025-05-15 23:52 ` Pawan Gupta
2025-05-16 15:06 ` Kaplan, David
2025-05-19 23:51 ` Pawan Gupta
2025-05-16 19:32 ` [PATCH v2] " David Kaplan
2025-05-16 22:47 ` Dave Hansen
2025-05-17 13:19 ` Ingo Molnar
2025-05-17 13:25 ` Borislav Petkov
2025-05-20 16:32 ` Pawan Gupta
2025-05-20 16:48 ` Borislav Petkov
2025-05-20 16:57 ` Pawan Gupta
2025-05-20 16:54 ` [tip: x86/core] " tip-bot2 for David Kaplan
2025-05-21 6:56 ` tip-bot2 for David Kaplan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250515220243.fk4z7rifcxdm2e7h@desk \
--to=pawan.kumar.gupta@linux.intel.com \
--cc=David.Kaplan@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®