From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>
Subject: Re: [PATCH 0/2] KVM: Fix dangling IRQ bypass on x86 and arm64
Date: Thu, 15 Jan 2026 10:03:19 -0800 [thread overview]
Message-ID: <176849868515.717654.3745446194809392090.b4-ty@google.com> (raw)
In-Reply-To: <20260113174606.104978-1-seanjc@google.com>
On Tue, 13 Jan 2026 09:46:04 -0800, Sean Christopherson wrote:
> Fix three bugs in one, where KVM can incorrectly leave an IRQ configured
> for bypass after the associated irqfd is deassigned from the VM (if the VMM
> deassigns the irqfd while it's in bypass mode).
>
> Two of the bugs are recent-ish, one each in x86 and arm64. The x86 bug is
> the most visible/noisy as it leads to kernel panics on AMD due to SVM's use
> of a per-CPU list to track IRQs/irqfds that are being posted to the vCPU.
>
> [...]
Applied rather quickly to kvm-x86 fixes, so that these can get as much time in
-next as possible. I'll wait until next week to send a pull request (hooray
for -rc8), and these are sitting at the top of the branch so I can amend (or
drop) them as needed.
[1/2] KVM: Don't clobber irqfd routing type when deassigning irqfd
https://github.com/kvm-x86/linux/commit/b4d37cdb77a0
[2/2] KVM: x86: Assert that non-MSI doesn't have bypass vCPU when deleting producer
https://github.com/kvm-x86/linux/commit/ef3719e33e66
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2026-01-15 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 17:46 Sean Christopherson
2026-01-13 17:46 ` [PATCH 1/2] KVM: Don't clobber irqfd routing type when deassigning irqfd Sean Christopherson
2026-01-13 17:46 ` [PATCH 2/2] KVM: x86: Assert that non-MSI doesn't have bypass vCPU when deleting producer Sean Christopherson
2026-01-15 18:03 ` Sean Christopherson [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=176849868515.717654.3745446194809392090.b4-ty@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@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
all inboxes | Powered by JetHome®