[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y1QA1RhqBYMkyEc8@hirez.programming.kicks-ass.net>
Date: Sat, 22 Oct 2022 16:40:21 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Hillf Danton <hdanton@...a.com>,
tip-bot2 for Peter Zijlstra <tip-bot2@...utronix.de>,
Seth Jenkins <sethjenkins@...gle.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Kees Cook <keescook@...omium.org>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [tip: x86/mm] x86/mm: Randomize per-cpu entry area
On Fri, Oct 21, 2022 at 05:56:02PM -0700, Dave Hansen wrote:
> On 10/21/22 17:00, Hillf Danton wrote:
> >> -#define CPU_ENTRY_AREA_MAP_SIZE (CPU_ENTRY_AREA_PER_CPU + CPU_ENTRY_AREA_ARRAY_SIZE - CPU_ENTRY_AREA_BASE)
> >> +#ifdef CONFIG_X86_32
> >> +#define CPU_ENTRY_AREA_MAP_SIZE (CPU_ENTRY_AREA_PER_CPU + \
> >> + (CPU_ENTRY_AREA_SIZE * NR_CPUS) - \
> >> + CPU_ENTRY_AREA_BASE
> > My vi editor finds un-paired bracket here.
> > Feel free to ignore it if nothing hurt.
>
> Thanks for finding that! Looks like Peter and I need to dust off our
> 32-bit .configs!
>
> I just fixed the issue and pushed a new commit out to tip/x86/mm.
Pff, I've had this commit exposed to 0day for a while, you'd think it
would scream. Then again, maybe it got lost in the email firehose :/
Powered by blists - more mailing lists