public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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,
	 syzbot+bc0e18379a290e5edfe4@syzkaller.appspotmail.com,
	 Xiaoyao Li <xiaoyao.li@intel.com>,
	Ethan Yang <ethan.yang.kernel@gmail.com>
Subject: [PATCH v3 0/3] KVM: x86: Async #PF MSR fix and cleanups
Date: Mon,  6 Apr 2026 15:53:55 -0700	[thread overview]
Message-ID: <20260406225359.1245490-1-seanjc@google.com> (raw)

Fix a user-triggerable WARN found syzkaller, then clean up related code
to eliminate potential stale data usage by removing what are effectively
duplicate fields.

Ethan Yang (1):
  KVM: x86: Don't leave APF half-enabled on bad APF data GPA

Sean Christopherson (2):
  KVM: x86: Drop superfluous caching of
    KVM_ASYNC_PF_DELIVERY_AS_PF_VMEXIT
  KVM: x86: Drop superfluous caching of KVM_ASYNC_PF_SEND_ALWAYS

 arch/x86/include/asm/kvm_host.h |  2 --
 arch/x86/kvm/x86.c              | 33 +++++++++++++++++----------------
 2 files changed, 17 insertions(+), 18 deletions(-)


base-commit: b89df297a47e641581ee67793592e5c6ae0428f4
-- 
2.53.0.1213.gd9a14994de-goog


             reply	other threads:[~2026-04-06 22:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 22:53 Sean Christopherson [this message]
2026-04-06 22:53 ` [PATCH v3 1/3] KVM: x86: Don't leave APF half-enabled on bad APF data GPA Sean Christopherson
2026-04-09  7:18   ` Binbin Wu
2026-04-06 22:53 ` [PATCH v3 2/3] KVM: x86: Drop superfluous caching of KVM_ASYNC_PF_DELIVERY_AS_PF_VMEXIT Sean Christopherson
2026-04-07 14:00   ` Xiaoyao Li
2026-04-09  7:25   ` Binbin Wu
2026-04-06 22:53 ` [PATCH v3 3/3] KVM: x86: Drop superfluous caching of KVM_ASYNC_PF_SEND_ALWAYS Sean Christopherson
2026-04-07 14:06   ` Xiaoyao Li
2026-04-09  7:42   ` Binbin Wu
2026-04-09  3:14 ` [PATCH v3 0/3] KVM: x86: Async #PF MSR fix and cleanups ethan_yang_kernel

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=20260406225359.1245490-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=ethan.yang.kernel@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=syzbot+bc0e18379a290e5edfe4@syzkaller.appspotmail.com \
    --cc=xiaoyao.li@intel.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