diff options
author | Marc Zyngier <maz@kernel.org> | 2024-10-02 23:42:39 +0300 |
---|---|---|
committer | Marc Zyngier <maz@kernel.org> | 2024-10-03 21:35:27 +0300 |
commit | a1d402abf8e3ff1d821e88993fc5331784fac0da (patch) | |
tree | 4ca519c66ebc14c1db58b26a604ebfd4e11a47f8 /tools/testing/selftests/hid/.gitignore | |
parent | 64a1d716615ee234a743b2528e95d8c3a9bef95f (diff) | |
download | linux-a1d402abf8e3ff1d821e88993fc5331784fac0da.tar.xz |
KVM: arm64: Fix kvm_has_feat*() handling of negative features
Oliver reports that the kvm_has_feat() helper is not behaviing as
expected for negative feature. On investigation, the main issue
seems to be caused by the following construct:
#define get_idreg_field(kvm, id, fld) \
(id##_##fld##_SIGNED ? \
get_idreg_field_signed(kvm, id, fld) : \
get_idreg_field_unsigned(kvm, id, fld))
where one side of the expression evaluates as something signed,
and the other as something unsigned. In retrospect, this is totally
braindead, as the compiler converts this into an unsigned expression.
When compared to something that is 0, the test is simply elided.
Epic fail. Similar issue exists in the expand_field_sign() macro.
The correct way to handle this is to chose between signed and unsigned
comparisons, so that both sides of the ternary expression are of the
same type (bool).
In order to keep the code readable (sort of), we introduce new
comparison primitives taking an operator as a parameter, and
rewrite the kvm_has_feat*() helpers in terms of these primitives.
Fixes: c62d7a23b947 ("KVM: arm64: Add feature checking helpers")
Reported-by: Oliver Upton <oliver.upton@linux.dev>
Tested-by: Oliver Upton <oliver.upton@linux.dev>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/20241002204239.2051637-1-maz@kernel.org
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/testing/selftests/hid/.gitignore')
0 files changed, 0 insertions, 0 deletions