From: Mukesh R <mrathor@linux.microsoft.com>
To: Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, longli@microsoft.com
Cc: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10] mshv: Bug fixes across the mshv_root module
Date: Wed, 29 Apr 2026 19:18:44 -0700 [thread overview]
Message-ID: <daacfbcc-e725-65f2-4b20-b4501e45e651@linux.microsoft.com> (raw)
In-Reply-To: <177748522635.144491.1565666089881726479.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net>
On 4/29/26 11:17, Stanislav Kinsburskii wrote:
> This series addresses bugs found during a review of the mshv_root module
> introduced by commit 621191d709b14 ("Drivers: hv: Introduce mshv_root
> module to expose /dev/mshv to VMMs").
>
> The fixes range from data corruption and use-after-free to silent
> functional failures:
>
> - IRQ state leak and type truncation in hypercall helpers
> (hv_call_modify_spa_host_access)
> - Integer overflow on userspace-controlled allocation size
> (mshv_region_create)
> - Missing locking, broken seqcount read protection, and a check on
> uninitialized data in the irqfd path ? the latter makes
> level-triggered interrupt resampling completely non-functional
> - Duplicate GSI 0 detection using the wrong predicate
> - Use-after-RCU in port ID lookup
> - Missing VP index bounds check in intercept ISR (OOB in interrupt
> context)
> - Missing error code on VP allocation failure (silent success to
> userspace)
Lot of changes here, curious, how were all these discovered
suddenly? Stress testing, internal/external? Or reported by
copilot/sashiko/etc..
How were the fixes tested?
Thanks,
-Mukesh
> ---
>
> Stanislav Kinsburskii (10):
> mshv: Fix IRQ leak and type hazards in hv_call_modify_spa_host_access
> mshv: Fix potential integer overflow in mshv_region_create
> mshv: Fix missing lock in mshv_irqfd_deassign
> mshv: Fix broken seqcount read protection
> mshv: Fix level-triggered check on uninitialized data
> mshv: Fix duplicate GSI detection for GSI 0
> mshv: Fix use-after-RCU in mshv_portid_lookup
> mshv: Use kfree_rcu in mshv_portid_free
> mshv: Add missing vp_index bounds check in intercept ISR
> mshv: Fix missing error code on VP allocation failure
>
>
> drivers/hv/mshv_eventfd.c | 75 ++++++++++++++++++++++------------------
> drivers/hv/mshv_irq.c | 2 +
> drivers/hv/mshv_portid_table.c | 6 +--
> drivers/hv/mshv_regions.c | 2 +
> drivers/hv/mshv_root_hv_call.c | 18 +++-------
> drivers/hv/mshv_root_main.c | 4 ++
> drivers/hv/mshv_synic.c | 4 ++
> 7 files changed, 59 insertions(+), 52 deletions(-)
>
next prev parent reply other threads:[~2026-04-30 2:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 18:17 [PATCH 00/10] mshv: Bug fixes across the mshv_root module Stanislav Kinsburskii
2026-04-29 18:17 ` [PATCH 01/10] mshv: Fix IRQ leak and type hazards in hv_call_modify_spa_host_access Stanislav Kinsburskii
2026-04-29 18:17 ` [PATCH 02/10] mshv: Fix potential integer overflow in mshv_region_create Stanislav Kinsburskii
2026-04-29 18:17 ` [PATCH 03/10] mshv: Fix missing lock in mshv_irqfd_deassign Stanislav Kinsburskii
2026-04-29 18:17 ` [PATCH 04/10] mshv: Fix broken seqcount read protection Stanislav Kinsburskii
2026-04-29 18:18 ` [PATCH 05/10] mshv: Fix level-triggered check on uninitialized data Stanislav Kinsburskii
2026-04-29 18:18 ` [PATCH 06/10] mshv: Fix duplicate GSI detection for GSI 0 Stanislav Kinsburskii
2026-04-29 18:18 ` [PATCH 07/10] mshv: Fix use-after-RCU in mshv_portid_lookup Stanislav Kinsburskii
2026-04-29 18:18 ` [PATCH 08/10] mshv: Use kfree_rcu in mshv_portid_free Stanislav Kinsburskii
2026-04-29 18:18 ` [PATCH 09/10] mshv: Add missing vp_index bounds check in intercept ISR Stanislav Kinsburskii
2026-04-29 18:18 ` [PATCH 10/10] mshv: Fix missing error code on VP allocation failure Stanislav Kinsburskii
2026-04-30 2:18 ` Mukesh R [this message]
2026-04-30 14:40 ` [PATCH 00/10] mshv: Bug fixes across the mshv_root module Stanislav Kinsburskii
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=daacfbcc-e725-65f2-4b20-b4501e45e651@linux.microsoft.com \
--to=mrathor@linux.microsoft.com \
--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=skinsburskii@linux.microsoft.com \
--cc=wei.liu@kernel.org \
/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