From: Nathan Chancellor <nathan@kernel.org>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
acdunlap@google.com, ashok.raj@intel.com, bp@alien8.de,
david@redhat.com, dionnaglaze@google.com, hpa@zytor.com,
jacobhxu@google.com, jgross@suse.com, jroedel@suse.de,
khalid.elmously@canonical.com, kim.phillips@amd.com,
kirill.shutemov@linux.intel.com, llvm@lists.linux.dev,
luto@kernel.org, mingo@redhat.com, nikunj@amd.com,
peterz@infradead.org, pgonda@google.com, rientjes@google.com,
rppt@kernel.org, seanjc@google.com, tglx@linutronix.de,
thomas.lendacky@amd.com, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] x86/boot: Move x86_cache_alignment initialization to correct spot
Date: Mon, 2 Oct 2023 15:24:02 -0700 [thread overview]
Message-ID: <20231002222402.GA486933@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20231002220045.1014760-1-dave.hansen@linux.intel.com>
On Mon, Oct 02, 2023 at 03:00:45PM -0700, Dave Hansen wrote:
> c->x86_cache_alignment is initialized from c->x86_clflush_size.
> However, commit fbf6449f84bf moved c->x86_clflush_size initialization
> to later in boot without moving the c->x86_cache_alignment assignment.
>
> This presumably left c->x86_cache_alignment set to zero for longer
> than it should be.
>
> The result was an oops on 32-bit kernels while accessing a pointer
> at 0x20. The 0x20 came from accessing a structure member at offset
> 0x10 (buffer->cpumask) from a ZERO_SIZE_PTR=0x10. kmalloc() can
> evidently return ZERO_SIZE_PTR when it's given 0 as its alignment
> requirement.
>
> Move the c->x86_cache_alignment initialization to be after
> c->x86_clflush_size has an actual value.
>
> Fixes: fbf6449f84bf ("x86/sev-es: Set x86_virt_bits to the correct value straight away, instead of a two-phase approach")
> Cc: Adam Dunlap <acdunlap@google.com>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Jacob Xu <jacobhxu@google.com>
> Link: https://lore.kernel.org/all/20231002200426.GA4127272@dev-arch.thelio-3990X/
Tested-by: Nathan Chancellor <nathan@kernel.org>
Thanks for the quick fix!
> ---
> arch/x86/kernel/cpu/common.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index 8d7063e4f63c9..9c51ad5bbf319 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -1141,6 +1141,7 @@ void get_cpu_address_sizes(struct cpuinfo_x86 *c)
> }
> }
> c->x86_cache_bits = c->x86_phys_bits;
> + c->x86_cache_alignment = c->x86_clflush_size;
> }
>
> static void identify_cpu_without_cpuid(struct cpuinfo_x86 *c)
> @@ -1594,8 +1595,6 @@ static void __init cpu_parse_early_param(void)
> */
> static void __init early_identify_cpu(struct cpuinfo_x86 *c)
> {
> - c->x86_cache_alignment = c->x86_clflush_size;
> -
> memset(&c->x86_capability, 0, sizeof(c->x86_capability));
> c->extended_cpuid_level = 0;
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-10-02 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230912002703.3924521-1-acdunlap@google.com>
[not found] ` <20230912002703.3924521-3-acdunlap@google.com>
2023-10-02 20:04 ` [PATCH v2 2/2] x86/sev-es: Only set x86_virt_bits to correct value Nathan Chancellor
2023-10-02 21:41 ` Dave Hansen
2023-10-02 21:46 ` Adam Dunlap
2023-10-02 22:00 ` [PATCH] x86/boot: Move x86_cache_alignment initialization to correct spot Dave Hansen
2023-10-02 22:24 ` Nathan Chancellor [this message]
2023-10-03 7:28 ` Ingo Molnar
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=20231002222402.GA486933@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=acdunlap@google.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dionnaglaze@google.com \
--cc=hpa@zytor.com \
--cc=jacobhxu@google.com \
--cc=jgross@suse.com \
--cc=jroedel@suse.de \
--cc=khalid.elmously@canonical.com \
--cc=kim.phillips@amd.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=peterz@infradead.org \
--cc=pgonda@google.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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