summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorFuad Tabba <fuad.tabba@linux.dev>2026-08-21 07:44:43 +0100
committerOliver Upton <oupton@kernel.org>2026-09-15 15:09:56 -0700
commit30908e7272479b6453745022abb9f2eb9c9933f7 (patch)
tree1947b930670d1b325c770a9ab217f19abfff7860 /tools/perf/scripts/python
parent8cd92f77ae4f5371a7d581f8324c24919670b304 (diff)
downloadlinux-next-30908e7272479b6453745022abb9f2eb9c9933f7.tar.gz
linux-next-30908e7272479b6453745022abb9f2eb9c9933f7.zip
Revert "KVM: arm64: vgic-its: Don't save collections the table cannot hold"
This reverts commit 9b10fb74e4b661543d188701bd4d024fc5c18f58. Freeing the collections when GITS_BASER<coll> changes removes the state this check rejected: vgic_its_cmd_handle_mapi(), vgic_its_cmd_handle_mapc() and vgic_its_restore_cte() all validate the ID against the current table before allocating, and the table can no longer change under the list. What remains is a collection whose entry is not backed by a memslot, which the write fails on anyway, so the check costs a save userspace should be able to issue reliably and buys nothing. The reverted commit credited the check with bounding the walk as well. It stays bounded without it: collection IDs are unique and each is below the table's capacity, so the list cannot be longer than the table. Suggested-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/all/87ecg9owwa.wl-maz@kernel.org/ Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev> Reviewed-by: Marc Zyngier <maz@kernel.org> Link: https://patch.msgid.link/20260821064445.615838-3-fuad.tabba@linux.dev Signed-off-by: Oliver Upton <oupton@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions