[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166951102250.2406619.18299131310725462090.b4-ty@chromium.org>
Date: Sat, 26 Nov 2022 17:03:44 -0800
From: Kees Cook <keescook@...omium.org>
To: gustavoars@...nel.org
Cc: Kees Cook <keescook@...omium.org>, mingo@...hat.com,
dave.hansen@...ux.intel.com, hpa@...or.com, luto@...nel.org,
tglx@...utronix.de, bp@...en8.de, peterz@...radead.org,
x86@...nel.org, linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] mm/pgtable: Fix multiple -Wstringop-overflow warnings
On Wed, 21 Sep 2022 13:46:03 -0500, Gustavo A. R. Silva wrote:
> The actual size of the following arrays at run-time depends on
> CONFIG_X86_PAE.
>
> 427 pmd_t *u_pmds[MAX_PREALLOCATED_USER_PMDS];
> 428 pmd_t *pmds[MAX_PREALLOCATED_PMDS];
>
> If CONFIG_X86_PAE is not enabled, their final size will be zero. In that
> case, the compiler complains about trying to access objects of size zero
> when calling functions where these objects are passed as arguments.
>
> [...]
Applied to for-next/hardening with tweaks to the commit log, thanks!
[1/1] mm/pgtable: Fix multiple -Wstringop-overflow warnings
https://git.kernel.org/kees/c/9af98f78d2cd
--
Kees Cook
Powered by blists - more mailing lists