diff options
| author | Fuad Tabba <fuad.tabba@linux.dev> | 2026-09-14 10:38:38 +0100 |
|---|---|---|
| committer | Oliver Upton <oupton@kernel.org> | 2026-09-15 15:09:57 -0700 |
| commit | 49d9d295d69d07e850cae35933ba8519e2915f26 (patch) | |
| tree | 1d7a374533e381a96d0a9c9d2425e62110188591 /tools/perf/scripts/python/task-analyzer.py | |
| parent | e5843f4effaa2ffac3e789ecd4456403564961d4 (diff) | |
| download | linux-next-49d9d295d69d07e850cae35933ba8519e2915f26.tar.gz linux-next-49d9d295d69d07e850cae35933ba8519e2915f26.zip | |
KVM: arm64: Don't WARN on an unknown VM ioctl in protected mode
kvm_pkvm_ioctl_allowed() WARNs when kvm_get_cap_for_kvm_ioctl() doesn't
find the ioctl number in vm_ioctl_caps[], and kvm_arch_vm_ioctl() calls
it for every number the generic code doesn't handle, so
ioctl(vm_fd, 0xdeadbeef) from userspace taints a pKVM host and panics it
under panic_on_warn. The lookup is fed userspace input: return false,
and userspace gets the -EINVAL kvm_arch_vm_ioctl() returns for that
number on a host without pKVM.
Fixes: b12b3b04f6ba0 ("KVM: arm64: Check whether a VM IOCTL is allowed in pKVM")
Cc: stable@vger.kernel.org
Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Link: https://patch.msgid.link/20260914093838.1082637-1-fuad.tabba@linux.dev
Signed-off-by: Oliver Upton <oupton@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions