mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Li,Rongqing" <lirongqing@baidu.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"bp@alien8.de" <bp@alien8.de>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"jpoimboe@kernel.org" <jpoimboe@kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"david.kaplan@amd.com" <david.kaplan@amd.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [????] Re: [PATCH][v2] x86/bugs: Fix GDS mitigation select for non-ARCH_CAP_GDS_CTRL CPUs
Date: Tue, 19 Aug 2025 02:03:07 +0000	[thread overview]
Message-ID: <455a7ad388c84d95887a5cede25f2825@baidu.com> (raw)
In-Reply-To: <20250818173302.33x5qvvw3mjmnixn@desk>



> -----Original Message-----
> From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> Sent: 2025年8月19日 1:33
> To: Li,Rongqing <lirongqing@baidu.com>
> Cc: tglx@linutronix.de; bp@alien8.de; peterz@infradead.org;
> jpoimboe@kernel.org; mingo@redhat.com; dave.hansen@linux.intel.com;
> x86@kernel.org; hpa@zytor.com; david.kaplan@amd.com;
> linux-kernel@vger.kernel.org
> Subject: [????] Re: [PATCH][v2] x86/bugs: Fix GDS mitigation select for
> non-ARCH_CAP_GDS_CTRL CPUs
> 
> On Sat, Aug 16, 2025 at 08:19:05AM +0800, lirongqing wrote:
> > From: Li RongQing <lirongqing@baidu.com>
> >
> > The current GDS mitigation logic incorrectly returns early when
> > ARCH_CAP_GDS_CTRL is not present, which leads to two problems:
> 
> ... not present? or the attack vector mitigation is turned off?


Should be "When the attack vector mitigation is turned off"

I will send v3, thanks

-Li

> 
> > 1. CPUs without ARCH_CAP_GDS_CTRL support are incorrectly marked with
> >    GDS_MITIGATION_OFF when they should be marked as
> >    GDS_MITIGATION_UCODE_NEEDED.
> >
> > 2. The mitigation state checks and locking verification that follow are
> >    skipped, which means:
> >    - fail to detect if the mitigation was locked
> >    - miss the warning when trying to disable a locked mitigation
> >
> > Remove the early return to ensure proper mitigation state handling.
> > This
> > allows:
> > - Proper mitigation classification for non-ARCH_CAP_GDS_CTRL CPUs
> > - Complete mitigation state verification
> >
> > The change fixes the following runtime issues observed:
> >
> > [    2.809147] unchecked MSR access error: WRMSR to 0x123 (tried to
> write 0x0000000000000010) at rIP: 0xffffffffb34527b8
> (update_gds_msr+0x38/0xe0)
> > [    2.809147] Call Trace:
> > [    2.809147]  <TASK>
> > [    2.809147]  identify_secondary_cpu+0x72/0x90
> > [    2.809147]  start_secondary+0x7a/0x140
> > [    2.809147]  common_startup_64+0x13e/0x141
> > [    2.809147]  </TASK>
> > [    2.809147] ------------[ cut here ]------------
> > [    2.809147] WARNING: CPU: 1 PID: 0 at
> arch/x86/kernel/cpu/bugs.c:1053 update_gds_msr+0x9b/0xe0
> >
> > Fixes: 8c7261abcb7ad ("x86/bugs: Add attack vector controls for GDS")
> > Suggested-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> 
> Reviewed-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>

      reply	other threads:[~2025-08-19  2:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16  0:19 lirongqing
2025-08-18 17:33 ` Pawan Gupta
2025-08-19  2:03   ` Li,Rongqing [this message]

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=455a7ad388c84d95887a5cede25f2825@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=david.kaplan@amd.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.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®