Re: [PATCH] kunit/stackinit: Use fill byte different from Clang i386 pattern

2025-03-05 Thread Kees Cook
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 0xF

Re: [PATCH] kunit/stackinit: Use fill byte different from Clang i386 pattern

2025-03-05 Thread Nathan Chancellor
On Tue, Mar 04, 2025 at 02:56:11PM -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 t

Re: [PATCH] kunit/stackinit: Use fill byte different from Clang i386 pattern

2025-03-04 Thread Kees Cook
On Tue, Mar 04, 2025 at 03:13:20PM -0800, Justin Stitt wrote: > Hi, > > On Tue, Mar 04, 2025 at 02:56:11PM -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

Re: [PATCH] kunit/stackinit: Use fill byte different from Clang i386 pattern

2025-03-04 Thread Justin Stitt
Hi, On Tue, Mar 04, 2025 at 02:56:11PM -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 inclu

[PATCH] kunit/stackinit: Use fill byte different from Clang i386 pattern

2025-03-04 Thread Kees Cook
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 th