summaryrefslogtreecommitdiff
path: root/fs/cramfs
diff options
context:
space:
mode:
authorZenghui Yu <yuzenghui@huawei.com>2019-10-29 10:19:19 +0300
committerMarc Zyngier <maz@kernel.org>2019-10-29 16:47:39 +0300
commitca185b260951d3b55108c0b95e188682d8a507b7 (patch)
tree478a1020713a0cf0bb46568973f6dea49c86f539 /fs/cramfs
parentbad36e4e8cdc9048948490293efefdbd85c40ecc (diff)
downloadlinux-ca185b260951d3b55108c0b95e188682d8a507b7.tar.xz
KVM: arm/arm64: vgic: Don't rely on the wrong pending table
It's possible that two LPIs locate in the same "byte_offset" but target two different vcpus, where their pending status are indicated by two different pending tables. In such a scenario, using last_byte_offset optimization will lead KVM relying on the wrong pending table entry. Let us use last_ptr instead, which can be treated as a byte index into a pending table and also, can be vcpu specific. Fixes: 280771252c1b ("KVM: arm64: vgic-v3: KVM_DEV_ARM_VGIC_SAVE_PENDING_TABLES") Cc: stable@vger.kernel.org Signed-off-by: Zenghui Yu <yuzenghui@huawei.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Acked-by: Eric Auger <eric.auger@redhat.com> Link: https://lore.kernel.org/r/20191029071919.177-4-yuzenghui@huawei.com
Diffstat (limited to 'fs/cramfs')
0 files changed, 0 insertions, 0 deletions