From: Tom Lendacky <thomas.lendacky@amd.com>
To: Borislav Petkov <bp@kernel.org>, X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
David Kaplan <david.kaplan@amd.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] x86/kexec: Fix bug with call depth tracking
Date: Mon, 3 Jun 2024 08:30:26 -0500 [thread overview]
Message-ID: <16622c3a-034e-9f78-3afa-b0c273ee4949@amd.com> (raw)
In-Reply-To: <20240603083036.637-1-bp@kernel.org>
On 6/3/24 03:30, Borislav Petkov wrote:
> From: David Kaplan <david.kaplan@amd.com>
>
> The call to cc_platform_has() triggers a fault and system crash if call depth
> tracking is active because the GS segment has been reset by load_segments() and
> GS_BASE is now 0 but call depth tracking uses per-CPU variables to operate.
>
> Call cc_platform_has() earlier in the function when GS is still valid.
>
> [ bp: Massage. ]
>
> Signed-off-by: David Kaplan <david.kaplan@amd.com>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Minor nit below, otherwise:
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
Does it need a Fixes: tag for call depth tracking (before the change to
cc_platform_has() it was a call to sme_active())?
> ---
> arch/x86/kernel/machine_kexec_64.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/machine_kexec_64.c b/arch/x86/kernel/machine_kexec_64.c
> index b180d8e497c3..90b1946c06e5 100644
> --- a/arch/x86/kernel/machine_kexec_64.c
> +++ b/arch/x86/kernel/machine_kexec_64.c
> @@ -295,8 +295,15 @@ void machine_kexec_cleanup(struct kimage *image)
> void machine_kexec(struct kimage *image)
> {
> unsigned long page_list[PAGES_NR];
> - void *control_page;
> + unsigned int host_mem_enc_active;
Looks like spaces used here instead of tabs.
Thanks,
Tom
> int save_ftrace_enabled;
> + void *control_page;
> +
> + /*
> + * This must be done before load_segments() since if call depth tracking
> + * is used then GS must be valid to make any function calls.
> + */
> + host_mem_enc_active = cc_platform_has(CC_ATTR_HOST_MEM_ENCRYPT);
>
> #ifdef CONFIG_KEXEC_JUMP
> if (image->preserve_context)
> @@ -358,7 +365,7 @@ void machine_kexec(struct kimage *image)
> (unsigned long)page_list,
> image->start,
> image->preserve_context,
> - cc_platform_has(CC_ATTR_HOST_MEM_ENCRYPT));
> + host_mem_enc_active);
>
> #ifdef CONFIG_KEXEC_JUMP
> if (image->preserve_context)
next prev parent reply other threads:[~2024-06-03 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 8:30 Borislav Petkov
2024-06-03 13:30 ` Tom Lendacky [this message]
2024-06-03 15:18 ` Borislav Petkov
2024-06-05 8:05 ` [tip: x86/urgent] " 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=16622c3a-034e-9f78-3afa-b0c273ee4949@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=david.kaplan@amd.com \
--cc=linux-kernel@vger.kernel.org \
--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®