[PATCH v4 1/3] randomize_kstack: Maintain kstack_offset per task
Dave Hansen
dave.hansen at intel.com
Mon Jan 19 08:53:33 PST 2026
On 1/19/26 08:51, Ryan Roberts wrote:
>> Since this doesn't fix any known functional issues, if it were me, I'd
>> leave stable@ alone. It isn't clear that this is stable material.
> I listed 2 issues in the commit log; I agree that issue 1 falls into the
> category of "don't really care", but issue 2 means that kstack randomization is
> currently trivial to defeat. That's the reason I thought it would valuable in
> stable.
>
> But if you're saying don't bother and others agree, then this whole patch can be
> dropped; this is just intended to be the backportable fix. Patch 3 reimplements
> this entirely for upstream.
>
> I'll wait and see if others have opinions if that's ok?
Sure. I don't feel that strongly about it.
More information about the linux-riscv
mailing list