From: Miko Larsson on
gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1923#note_1049...
That's the rebase, we do it every .0 release.
Oh, I see.
Thanks!
Sorry I have not commented on this yet, as I was on vacation last
week, and we are now going into the merge window/test week madness. I
am certainly not against the intent of the change, but I am concerned
on the cost. I need to do some research. So do not be surprised if
this sits here for a few weeks, but I will have an answer one way or
the other before 6.0.
For what it's worth, I'm aware that Google uses
INIT_STACK_ALL(_ZERO)
for their Android kernels, and they note that unnecessary
initializations are optimized away by the compiler.[1] They do build
their kernels with clang though, so it's not *impossible* that gcc
might behave differently.
1.
https://source.android.com/security/memory-safety/zero-initialized-memory