summaryrefslogtreecommitdiff
path: root/scripts/patch-kernel
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2022-05-28 12:38:11 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-06-22 14:28:11 +0200
commit179d8d27a6bfdc61db83949ea8152583fcfd3951 (patch)
tree72bcc6cb238609bbeab3f772ea162f97542aa309 /scripts/patch-kernel
parentaf75c481a2e45e70f62f5942c93695e95bf7bd21 (diff)
KVM: arm64: Always start with clearing SVE flag on load
commit d52d165d67c5aa26c8c89909003c94a66492d23d upstream. On each vcpu load, we set the KVM_ARM64_HOST_SVE_ENABLED flag if SVE is enabled for EL0 on the host. This is used to restore the correct state on vpcu put. However, it appears that nothing ever clears this flag. Once set, it will stick until the vcpu is destroyed, which has the potential to spuriously enable SVE for userspace. We probably never saw the issue because no VMM uses SVE, but that's still pretty bad. Unconditionally clearing the flag on vcpu load addresses the issue. Fixes: 8383741ab2e7 ("KVM: arm64: Get rid of host SVE tracking/saving") Signed-off-by: Marc Zyngier <maz@kernel.org> Cc: stable@vger.kernel.org Reviewed-by: Mark Brown <broonie@kernel.org> Link: https://lore.kernel.org/r/20220528113829.1043361-2-maz@kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/patch-kernel')
0 files changed, 0 insertions, 0 deletions