Fix off-by-one in range_is_memory
Status from this message: Applied to kvm-arm64/mmu/el2-tracking, thanks!
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | KVM: arm64: Fix off-by-one in range_is_memoryarch/ | +1 | 1 reply | |
| 2/2 | KVM: arm64: Minor optimization of range_is_memoryarch/ | +8 | 1 reply |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Quentin Perret |
|---|---|
| 1/2 | R-b |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] Fix off-by-one in range_is_memory
Hi, here is an off-by-one bug fix and a very minor improvement for the range_is_memory function in hyp.
David Brazdil (2):
KVM: arm64: Fix off-by-one in range_is_memory
KVM: arm64: Minor optimization of range_is_memory
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)
Signature · 1 line
2.32.0.432.gabb21c7263-goog