From: Wei Liu <wei.liu@kernel.org>
To: Nuno Das Neves <nunodasneves@linux.microsoft.com>
Cc: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
mhklinux@outlook.com, magnuskulke@linux.microsoft.com,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, longli@microsoft.com,
skinsburskii@linux.microsoft.com, prapal@linux.microsoft.com,
mrathor@linux.microsoft.com, muislam@microsoft.com
Subject: Re: [PATCH v2 0/2] mshv: Allow mappings that overlap in uaddr
Date: Fri, 7 Nov 2025 18:13:04 +0000 [thread overview]
Message-ID: <20251107181304.GB4041739@liuwe-devbox-debian-v2.local> (raw)
In-Reply-To: <1762467211-8213-1-git-send-email-nunodasneves@linux.microsoft.com>
On Thu, Nov 06, 2025 at 02:13:29PM -0800, Nuno Das Neves wrote:
> Currently the MSHV driver rejects mappings that would overlap in
> userspace. Remove this limitation as it is overly restrictive and
> allowing overlap is useful for VMMs.
>
> Before make this change, fix the region overlap checking logic
> which is broken.
>
> ---
> Changes in v2:
> - Add a patch to fix the overlap checking [Michael Kelley]
> - Move deletion of mshv_partition_region_by_uaddr() to the fix patch
>
> ---
> Magnus Kulke (1):
> mshv: Allow mappings that overlap in uaddr
>
> Nuno Das Neves (1):
> mshv: Fix create memory region overlap check
Applied to hyperv-next. Thanks.
>
> drivers/hv/mshv_root_main.c | 27 +++++++--------------------
> include/uapi/linux/mshv.h | 2 +-
> 2 files changed, 8 insertions(+), 21 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2025-11-07 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 22:13 [PATCH v2 0/2] mshv: Allow mappings that overlap in uaddr Nuno Das Neves
2025-11-06 22:13 ` [PATCH v2 1/2] mshv: Fix create memory region overlap check Nuno Das Neves
2025-11-07 15:24 ` Michael Kelley
2025-11-06 22:13 ` [PATCH v2 2/2] mshv: Allow mappings that overlap in uaddr Nuno Das Neves
2025-11-07 15:25 ` Michael Kelley
2025-11-07 18:13 ` Wei Liu [this message]
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=20251107181304.GB4041739@liuwe-devbox-debian-v2.local \
--to=wei.liu@kernel.org \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=magnuskulke@linux.microsoft.com \
--cc=mhklinux@outlook.com \
--cc=mrathor@linux.microsoft.com \
--cc=muislam@microsoft.com \
--cc=nunodasneves@linux.microsoft.com \
--cc=prapal@linux.microsoft.com \
--cc=skinsburskii@linux.microsoft.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;
as well as URLs for NNTP newsgroup(s).