From: Vincent Donnefort <vdonnefort@google.com>
To: maz@kernel.org, oliver.upton@linux.dev, joey.gouly@arm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
catalin.marinas@arm.com, will@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kernel-team@android.com,
Vincent Donnefort <vdonnefort@google.com>
Subject: [PATCH v2 0/3] Fixes for hyp_trace.c
Date: Thu, 21 May 2026 13:46:10 +0100 [thread overview]
Message-ID: <20260521124613.911067-1-vdonnefort@google.com> (raw)
While reviewing my v1, Sashiko found a couple of issues with the error path and
more annoyingly a memory leak which I originally missed as the allocated
decriptor isn't tracked by kmemleak.
Changes since v2:
- Fix rollback in hyp_trace_buffer_share_hyp()
- Fix memory leak in hyp_trace_unload()
v1 (https://lore.kernel.org/all/20260521090939.735108-1-vdonnefort@google.com/)
Vincent Donnefort (3):
KVM: arm64: Fix meta-page unsharing in pKVM hyp tracing
KVM: arm64: Fix rollback in hyp_trace_buffer_share_hyp()
KVM: arm64: Fix memory leak in hyp_trace_unload()
arch/arm64/kvm/hyp_trace.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
base-commit: 5200f5f493f79f14bbdc349e402a40dfb32f23c8
--
2.54.0.746.g67dd491aae-goog
next reply other threads:[~2026-05-21 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 12:46 Vincent Donnefort [this message]
2026-05-21 12:46 ` [PATCH v2 1/3] KVM: arm64: Fix meta-page unsharing in pKVM hyp tracing Vincent Donnefort
2026-05-21 12:46 ` [PATCH v2 2/3] KVM: arm64: Fix rollback in hyp_trace_buffer_share_hyp() Vincent Donnefort
2026-05-21 12:46 ` [PATCH v2 3/3] KVM: arm64: Fix memory leak in hyp_trace_unload() Vincent Donnefort
2026-05-27 13:13 ` [PATCH v2 0/3] Fixes for hyp_trace.c Marc Zyngier
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=20260521124613.911067-1-vdonnefort@google.com \
--to=vdonnefort@google.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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