From: ZongYao.Chen@linux.alibaba.com
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: Shuah Khan <shuah@kernel.org>,
Sean Christopherson <seanjc@google.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Xiaoyao Li <xiaoyao.li@intel.com>,
Ackerley Tng <ackerleytng@google.com>,
Tianjia Zhang <tianjia.zhang@linux.alibaba.com>,
Zongyao Chen <ZongYao.Chen@linux.alibaba.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] KVM: selftests: Test guest_memfd binding overlap without GPA overlap
Date: Mon, 18 May 2026 15:09:43 +0800 [thread overview]
Message-ID: <20260518070943.2091287-3-ZongYao.Chen@linux.alibaba.com> (raw)
In-Reply-To: <20260518070943.2091287-1-ZongYao.Chen@linux.alibaba.com>
From: Zongyao Chen <ZongYao.Chen@linux.alibaba.com>
The guest_memfd binding overlap test recreates the deleted slot with GPA
ranges that overlap the still-live slot. KVM rejects those attempts from
the generic memslot overlap check before reaching kvm_gmem_bind(), so the
test can pass even if guest_memfd binding overlap detection is broken.
Recreate the slot at its original, non-overlapping GPA and use guest_memfd
offsets that overlap the front and back halves of the other slot's binding.
Expand the guest_memfd so the back-half case remains within the file size.
Fixes: 2feabb855df8 ("KVM: selftests: Expand set_memory_region_test to validate guest_memfd()")
Signed-off-by: Zongyao Chen <ZongYao.Chen@linux.alibaba.com>
---
.../testing/selftests/kvm/set_memory_region_test.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/tools/testing/selftests/kvm/set_memory_region_test.c b/tools/testing/selftests/kvm/set_memory_region_test.c
index 9b919a231c93..15607e0bec90 100644
--- a/tools/testing/selftests/kvm/set_memory_region_test.c
+++ b/tools/testing/selftests/kvm/set_memory_region_test.c
@@ -510,7 +510,7 @@ static void test_add_overlapping_private_memory_regions(void)
vm = vm_create_barebones_type(KVM_X86_SW_PROTECTED_VM);
- memfd = vm_create_guest_memfd(vm, MEM_REGION_SIZE * 4, 0);
+ memfd = vm_create_guest_memfd(vm, MEM_REGION_SIZE * 6, 0);
vm_set_user_memory_region2(vm, MEM_REGION_SLOT, KVM_MEM_GUEST_MEMFD,
MEM_REGION_GPA, MEM_REGION_SIZE * 2, 0, memfd, 0);
@@ -526,19 +526,19 @@ static void test_add_overlapping_private_memory_regions(void)
vm_set_user_memory_region2(vm, MEM_REGION_SLOT, KVM_MEM_GUEST_MEMFD,
MEM_REGION_GPA, 0, NULL, -1, 0);
- /* Overlap the front half of the other slot. */
+ /* Overlap the front half of the other slot's guest_memfd binding. */
r = __vm_set_user_memory_region2(vm, MEM_REGION_SLOT, KVM_MEM_GUEST_MEMFD,
- MEM_REGION_GPA * 2 - MEM_REGION_SIZE,
+ MEM_REGION_GPA,
MEM_REGION_SIZE * 2,
- 0, memfd, 0);
+ 0, memfd, MEM_REGION_SIZE);
TEST_ASSERT(r == -1 && errno == EEXIST, "%s",
"Overlapping guest_memfd() bindings should fail with EEXIST");
- /* And now the back half of the other slot. */
+ /* And now the back half of the other slot's guest_memfd binding. */
r = __vm_set_user_memory_region2(vm, MEM_REGION_SLOT, KVM_MEM_GUEST_MEMFD,
- MEM_REGION_GPA * 2 + MEM_REGION_SIZE,
+ MEM_REGION_GPA,
MEM_REGION_SIZE * 2,
- 0, memfd, 0);
+ 0, memfd, MEM_REGION_SIZE * 3);
TEST_ASSERT(r == -1 && errno == EEXIST, "%s",
"Overlapping guest_memfd() bindings should fail with EEXIST");
--
2.47.3
next prev parent reply other threads:[~2026-05-18 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 7:09 [PATCH 0/2] KVM: Fix guest_memfd binding overlap errno and selftest ZongYao.Chen
2026-05-18 7:09 ` [PATCH 1/2] KVM: guest_memfd: Return -EEXIST for overlapping bindings ZongYao.Chen
2026-05-18 18:32 ` Sean Christopherson
2026-05-18 20:11 ` Ackerley Tng
2026-05-18 7:09 ` ZongYao.Chen [this message]
2026-05-18 20:05 ` [PATCH 2/2] KVM: selftests: Test guest_memfd binding overlap without GPA overlap Ackerley Tng
2026-05-18 20:39 ` Sean Christopherson
2026-05-19 18:35 ` Ackerley Tng
2026-05-19 19:54 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260518070943.2091287-3-ZongYao.Chen@linux.alibaba.com \
--to=zongyao.chen@linux.alibaba.com \
--cc=ackerleytng@google.com \
--cc=chao.p.peng@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tianjia.zhang@linux.alibaba.com \
--cc=xiaoyao.li@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®