[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174124111820.371215.12037584866390434063.b4-ty@kernel.org>
Date: Wed, 5 Mar 2025 22:05:22 -0800
From: Kees Cook <kees@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>,
Kees Cook <kees@...nel.org>
Cc: Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>,
llvm@...ts.linux.dev,
Geert Uytterhoeven <geert+renesas@...der.be>,
David Gow <davidgow@...gle.com>,
"Masami Hiramatsu (Google)" <mhiramat@...nel.org>,
Jeff Johnson <quic_jjohnson@...cinc.com>,
Ard Biesheuvel <ardb@...nel.org>,
linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH] kunit/stackinit: Use fill byte different from Clang i386 pattern
On Tue, 04 Mar 2025 14:56:11 -0800, Kees Cook wrote:
> The byte initialization values used with -ftrivial-auto-var-init=pattern
> (CONFIG_INIT_STACK_ALL_PATTERN=y) depends on the compiler, architecture,
> and byte position relative to struct member types. On i386 with Clang,
> this includes the 0xFF value, which means it looks like nothing changes
> between the leaf byte filling pass and the expected "stack wiping"
> pass of the stackinit test.
>
> [...]
Applied to for-next/move-kunit-tests.
[1/1] kunit/stackinit: Use fill byte different from Clang i386 pattern
https://git.kernel.org/kees/c/d985e4399adf
--
Kees Cook
Powered by blists - more mailing lists