From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: lirongqing <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][v3] x86/bugs: Fix GDS mitigation selecting when mitigation is off
Date: Mon, 18 Aug 2025 22:28:07 -0700 [thread overview]
Message-ID: <20250819052807.mpqdtauhs33uxnay@desk> (raw)
In-Reply-To: <20250819023356.2012-1-lirongqing@baidu.com>
On Tue, Aug 19, 2025 at 10:33:56AM +0800, lirongqing wrote:
> From: Li RongQing <lirongqing@baidu.com>
>
> The current GDS mitigation logic incorrectly returns early when the
> attack vector mitigation is turned off, which leads to two problems:
>
> 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 because mitigation is off
> in non-ARCH_CAP_GDS_CTRL CPUs:
>
> [ 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>
> Reviewed-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> Diff with v2: refine the commit header and Reviewed-by: Pawan Gupta
> Diff with v1: directly remove return
>
> arch/x86/kernel/cpu/bugs.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/bugs.c b/arch/x86/kernel/cpu/bugs.c
> index b74bf93..9e0b9bf 100644
> --- a/arch/x86/kernel/cpu/bugs.c
> +++ b/arch/x86/kernel/cpu/bugs.c
> @@ -1071,7 +1071,6 @@ static void __init gds_select_mitigation(void)
> gds_mitigation = GDS_MITIGATION_FULL;
> else {
> gds_mitigation = GDS_MITIGATION_OFF;
> - return;
> }
With the "return" gone, braces are not needed in the "else" block (although
it is a bit strange to have braces only in the "else" block to begin with).
Sorry, I missed to spot that in the previous review.
next prev parent reply other threads:[~2025-08-19 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 2:33 [PATCH][v3] x86/bugs: Fix GDS mitigation selecting when mitigation is off lirongqing
2025-08-19 5:28 ` Pawan Gupta [this message]
2025-08-19 9:11 ` [tip: x86/urgent] " tip-bot2 for Li RongQing
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=20250819052807.mpqdtauhs33uxnay@desk \
--to=pawan.kumar.gupta@linux.intel.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=lirongqing@baidu.com \
--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;
as well as URLs for NNTP newsgroup(s).