From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KVM: Fixes for 7.3-rcN
Date: Mon, 28 Sep 2026 08:41:34 -0700 [thread overview]
Message-ID: <arqKrvYupBpAM2WI@google.com> (raw)
In-Reply-To: <CABgObfZeA_q_prxJhbdNqYpE8quPD360LhVBQv8ypcPpLA-Mhg@mail.gmail.com>
On Sat, Sep 26, 2026, Paolo Bonzini wrote:
> On Sat, Sep 26, 2026 at 1:33 AM Sean Christopherson <seanjc@google.com> wrote:
> >
> > Please pull a variety of fixes. Nothing is super urgent, but all of these can
> > be fatal to the host and/or guest (except for the selftest change, which fixes
> > a regression that was introduced in 7.3).
> >
> > The following changes since commit d599822bdb66aeec5ec76297b0fc6efaaeefe07c:
> >
> > Merge tag 'kvm-s390-master-7.3-1' of https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD (2026-09-04 17:34:28 +0200)
> >
> > are available in the Git repository at:
> >
> > https://github.com/kvm-x86/linux.git tags/kvm-x86-fixes-7.3-rc5
> >
> > for you to fetch changes up to 119e9db233ad0f4cbd4cfb9f9385a7bca378b37d:
> >
> > KVM: Don't pre-reserve xarray entries when storing empty/NULL attributes (2026-09-22 08:36:16 -0700)
>
> Pulled, thanks. I added on top the SEV cache writeback patches which
> are not present here.
Heh, because they're buggy. Sashiko pointed out flaws in both[1][2]. I have
fixes (will send them shortly); I was late on posting v2 because it took me forever
to figure out a not-awful solution for the double-free issue due to the annoying
CONFIG_CPUMASK_OFFSTACK behavior.
[1] https://lore.kernel.org/all/20260923165304.1662E1F000FF@smtp.kernel.org
[2] https://lore.kernel.org/all/20260923165349.CAAF01F000FF@smtp.kernel.org
next prev parent reply other threads:[~2026-09-28 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 23:33 [GIT PULL] KVM: Fixes for 7.3-rcN Sean Christopherson
2026-09-26 4:40 ` Paolo Bonzini
2026-09-28 15:41 ` Sean Christopherson [this message]
2026-09-28 15:56 ` Paolo Bonzini
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=arqKrvYupBpAM2WI@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.