On Wed, 22 Oct 2025 08:48:34 +0300 Mike Rapoport rppt@kernel.org wrote:
We are using KHO and have had obscure crashes due to this memory corruption, with stacks all over the place. I would prefer this fix to be properly backported to stable so we can also automatically consume it once we switch to the upstream KHO. I do not think disabling kfence in the Google fleet to resolve this problem would work for us, so if it is not going to be part of stable, we would have to backport it manually anyway.
The backport to stable is only relevant to 6.17 that's going to be EOL soon anyway. Do you really think it's worth the effort?
If some organization is basing their next kernel on 6.17 then they'd like it.
Do we assume that all organizations follow the LTS schedule? I haven't been doing that.