diff options
author | 2025-01-10 16:29:59 -0800 | |
---|---|---|
committer | 2025-02-12 09:00:56 -0800 | |
commit | 485e27ed208f0d9667608c0e3fa9440654e01399 (patch) | |
tree | 77e69e7ba9e29cb7950c3c72e1e7969d869341a1 | |
parent | KVM: selftests: Collect *all* dirty entries in each dirty_log_test iteration (diff) | |
download | wireguard-linux-485e27ed208f0d9667608c0e3fa9440654e01399.tar.xz wireguard-linux-485e27ed208f0d9667608c0e3fa9440654e01399.zip |
KVM: sefltests: Verify value of dirty_log_test last page isn't bogus
Add a sanity check that a completely garbage value wasn't written to
the last dirty page in the ring, e.g. that it doesn't contain the *next*
iteration's value.
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Link: https://lore.kernel.org/r/20250111003004.1235645-16-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
-rw-r--r-- | tools/testing/selftests/kvm/dirty_log_test.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/tools/testing/selftests/kvm/dirty_log_test.c b/tools/testing/selftests/kvm/dirty_log_test.c index 3a4e411353d7..500257b712e3 100644 --- a/tools/testing/selftests/kvm/dirty_log_test.c +++ b/tools/testing/selftests/kvm/dirty_log_test.c @@ -514,8 +514,9 @@ static void vm_dirty_log_verify(enum vm_guest_mode mode, unsigned long **bmap) * last page's iteration), as the value to be * written may be cached in a CPU register. */ - if (page == dirty_ring_last_page || - page == dirty_ring_prev_iteration_last_page) + if ((page == dirty_ring_last_page || + page == dirty_ring_prev_iteration_last_page) && + val < iteration) continue; } else if (!val && iteration == 1 && bmap0_dirty) { /* |