diff options
| author | Fuad Tabba <fuad.tabba@linux.dev> | 2026-10-13 17:43:34 +0100 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2026-10-17 16:49:10 +0100 |
| commit | 09d5e940500c2e51b697a0522c54132c1ef078ef (patch) | |
| tree | 0cf9acb7f24e73bbc09145b14eadad8c2283b8fe /scripts/basic/split-include.c | |
| parent | fd73f4a6659897191fa0d40695fe370925dd3780 (diff) | |
| download | linux-09d5e940500c2e51b697a0522c54132c1ef078ef.tar.gz linux-09d5e940500c2e51b697a0522c54132c1ef078ef.zip | |
KVM: arm64: Don't WARN on SMCCC filter reserved range allocation failure
The first time userspace sets an SMCCC filter, kvm_smccc_set_filter()
inserts the reserved architecture ranges into the maple tree and WARNs
if that fails. The insertion allocates with GFP_KERNEL_ACCOUNT, so a
tight memory cgroup limit is enough for userspace to hit the WARN, even
though the -ENOMEM is also returned to it. The WARN dates back to when
the ranges were inserted at VM creation.
Leave -ENOMEM out of the WARN and keep it for every other error. The
two reserved ranges are fixed and disjoint and go into an empty tree
under config_lock, so any other error is a KVM bug.
Fixes: fb88707dd39bd ("KVM: arm64: Use a maple tree to represent the SMCCC filter")
Reported-by: Sashiko <sashiko-bot@kernel.org>
Closes: https://lore.kernel.org/all/20260829055809.29AD31F000E9@smtp.kernel.org/
Suggested-by: Oliver Upton <oupton@kernel.org>
Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Reviewed-by: Oliver Upton <oupton@kernel.org>
Link: https://patch.msgid.link/20261013164334.1492070-1-fuad.tabba@linux.dev
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'scripts/basic/split-include.c')
0 files changed, 0 insertions, 0 deletions
