[PATCH v4 0/3] Fix bugs and performance of kstack offset randomisation

Dave Hansen dave.hansen at intel.com
Tue Jan 20 08:37:43 PST 2026


On 1/20/26 08:32, Ryan Roberts wrote:
> I don't think this question was really addressed to me, but I'll give my opinion
> anyway; I agree it's pretty binary - it will either work or it will explode.
> I've tested on arm64 and x86_64 so I have high confidence that it works. If you
> get it into -next ASAP it has 3 weeks to soak before the merge window opens
> right? (Linus said he would do an -rc8 this cycle). That feels like enough time
> to me. But it's your tree 😉

First of all, thank you for testing it on x86! Having that one data
point where it helped performance is super valuable.

I'm more worried that it's going to regress performance somewhere and
then it's going to be a pain to back out. I'm not super worried about
functional regressions.



More information about the linux-riscv mailing list