From: Oliver Upton <oliver.upton@linux.dev>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM/arm64 changes for 6.17, round #3
Date: Wed, 17 Sep 2025 12:58:07 -0700 [thread overview]
Message-ID: <aMsSz9YUcd4Qf0ND@linux.dev> (raw)
In-Reply-To: <6e598aec-f55c-467a-abef-6d183bb9cfca@redhat.com>
On Wed, Sep 17, 2025 at 07:56:15PM +0200, Paolo Bonzini wrote:
> On 9/10/25 22:25, Oliver Upton wrote:
> > Hi Paolo,
> >
> > This is most likely the final set of KVM/arm64 fixes for 6.17.
> >
> > Of note, I reverted a couple of fixes we took in 6.17 for RCU stalls when
> > destroying a stage-2 page table. There appears to be some nasty refcounting /
> > UAF issues lurking in those patches and the band-aid we tried to apply didn't
> > hold.
>
> Thanks for pointing this out, I will put a note about reverts in my own tag.
Appreciated, seems to have been an unintentional omission from my own
tag.
Best,
Oliver
prev parent reply other threads:[~2025-09-17 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 20:25 [GIT PULL] KVM/arm64 changes for 6.17, round #3 Oliver Upton
2025-09-17 17:56 ` Paolo Bonzini
2025-09-17 19:58 ` Oliver Upton [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=aMsSz9YUcd4Qf0ND@linux.dev \
--to=oliver.upton@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.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