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 0/2] KVM: Fix guest_memfd binding overlap errno and selftest
Date: Mon, 18 May 2026 15:09:41 +0800 [thread overview]
Message-ID: <20260518070943.2091287-1-ZongYao.Chen@linux.alibaba.com> (raw)
From: Zongyao Chen <ZongYao.Chen@linux.alibaba.com>
KVM rejects guest_memfd bindings that overlap an existing binding, but
currently reports -EINVAL from the generic error path. Return -EEXIST for
binding conflicts and adjust the selftest so it actually reaches the
guest_memfd binding overlap check instead of failing earlier on GPA memslot
overlap.
Zongyao Chen (2):
KVM: guest_memfd: Return -EEXIST for overlapping bindings
KVM: selftests: Test guest_memfd binding overlap without GPA overlap
.../testing/selftests/kvm/set_memory_region_test.c | 14 +++++++-------
virt/kvm/guest_memfd.c | 1 +
2 files changed, 8 insertions(+), 7 deletions(-)
base-commit: 1d5dcaa3bd65f2e8c9baa14a393d3a2dc5db7524
--
2.47.3
next reply other threads:[~2026-05-18 7:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 7:09 ZongYao.Chen [this message]
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 ` [PATCH 2/2] KVM: selftests: Test guest_memfd binding overlap without GPA overlap ZongYao.Chen
2026-05-18 20:05 ` 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-1-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®