Re: hunting memory corruption bug in 6.18.x

[Lorenzo Stoakes (ARM)]

On Tue, Sep 29, 2026 at 09:11:53PM +0200, Nikola Ciprich wrote:

> so he reverted back to 6.18.15
>
> then he got crash of another node (to which he was migrating VMs from the first updated node), that one
> was still running 6.18.15
>
> pretty unfortunate planned work outcome :-/
>
> but it confirms that both 6.18.15 and unfortunately also 6.18.54 are affected

Yeah 6.18.15 is expected, I'd not say reverting is really worthwhile honestly,
given what you've observed previously.

Maybe worth checking if commit 26505e1b5b54 ("KVM: SVM: make svm_flush_tlb_gva
do a full asid flush if NPT enabled") helps in that case?

--
Cheers, Lorenzo