From: David Laight <david.laight.linux@gmail.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Replace BUG_ON() with WARN_ON_ONCE() on "bad" nested GPA translation
Date: Fri, 19 Jun 2026 16:06:45 +0100 [thread overview]
Message-ID: <20260619160645.57f4e325@pumpkin> (raw)
In-Reply-To: <20260618185746.2023283-1-seanjc@google.com>
On Thu, 18 Jun 2026 11:57:45 -0700
Sean Christopherson <seanjc@google.com> wrote:
> If KVM attempts to translate what it thinks is an L2 GPA with a non-nested
> MMU, simply WARN and return the GPA, i.e. trust the MMU more than the
> caller, as there is zero reason to potentially panic the host kernel just
> because KVM misused an API.
Except that PANIC_ON_WARN stands a reasonable chance of being set.
So it makes little difference.
David
>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/kvm/svm/nested.c | 3 ++-
> arch/x86/kvm/vmx/nested.c | 3 ++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/nested.c b/arch/x86/kvm/svm/nested.c
> index 9aedb88c832d..3e6c671a8dc2 100644
> --- a/arch/x86/kvm/svm/nested.c
> +++ b/arch/x86/kvm/svm/nested.c
> @@ -2152,7 +2152,8 @@ static gpa_t svm_translate_nested_gpa(struct kvm_vcpu *vcpu, gpa_t gpa,
> struct vcpu_svm *svm = to_svm(vcpu);
> struct kvm_mmu *mmu = vcpu->arch.mmu;
>
> - BUG_ON(!mmu_is_nested(vcpu));
> + if (WARN_ON_ONCE(!mmu_is_nested(vcpu)))
> + return gpa;
>
> /* Non-GMET walks are always user-walks */
> if (!(svm->nested.ctl.misc_ctl & SVM_MISC_ENABLE_GMET))
> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> index 3a293640d58c..6957bb6f5cf7 100644
> --- a/arch/x86/kvm/vmx/nested.c
> +++ b/arch/x86/kvm/vmx/nested.c
> @@ -7470,7 +7470,8 @@ static gpa_t vmx_translate_nested_gpa(struct kvm_vcpu *vcpu, gpa_t gpa,
> {
> struct kvm_mmu *mmu = vcpu->arch.mmu;
>
> - BUG_ON(!mmu_is_nested(vcpu));
> + if (WARN_ON_ONCE(!mmu_is_nested(vcpu)))
> + return gpa;
>
> /*
> * MBEC differentiates based on the effective U/S bit of
>
> base-commit: 9d4853b044beefa21c4ee3e18c40653601a64ced
prev parent reply other threads:[~2026-06-19 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 18:57 [PATCH] KVM: x86: Replace BUG_ON() with WARN_ON_ONCE() on "bad" nested GPA translation Sean Christopherson
2026-06-19 4:26 ` Huang, Kai
2026-06-19 15:06 ` David Laight [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=20260619160645.57f4e325@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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.