From: SimonP <simonp.git@mailbox.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>, kvm@vger.kernel.org
Subject: Re: [REGRESSION 7.2, BISECTED] KVM: x86: Starting Windows guest triggers UBSAN: array-index-out-of-bounds
Date: Thu, 8 Oct 2026 17:53:20 +0200 [thread overview]
Message-ID: <ase8Jrg2BBru6lg3@mailbox.org> (raw)
In-Reply-To: <CABgObfYMRUzDSUPY7MMp2fbRbU+eMCdDVZT9vQxUcT_Bwm9z_Q@mail.gmail.com>
On Wed, Oct 07, 2026 at 01:18:03PM +0200, Paolo Bonzini wrote:
> On Wed, Oct 7, 2026 at 1:16 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> > On Tue, Oct 6, 2026 at 7:37 PM SimonP <simonp.git@mailbox.org> wrote:
> > > Hello,
> > >
> > > See subject. Happens in permission_fault() on line:
> > >
> > > fault = (mmu->permissions[index] >> pte_access) & 1;
> > >
> > > Some output from a printk I added, not spammed but keeps happening:
> > >
> > > kvm: permission_fault(): pfec = 70, index = 35, not_smap = 0
> >
> > Can you confirm you are using nested virtualization, and if so what is
> > the L1 hypervisor and L2 guest combination? Also what is the processor
> > model?
> >
> > The issue is weird; it is caused by the SS bit which is apparently set
> > in the #NPF exitcode; but it shouldn't be unless bit 4 is set in the
> > misc_ctl field, and KVM never sets it. Can you check if the attached
> > patch fixes it (modulo the fact that it shouldn't happen in the first
> > place)?
>
> Attachment added now.
Patch is good. UBSAN doesn't complain anymore, no WARN is hit, and the
guest works.
Regards,
Simon
>
> Paolo
next prev parent reply other threads:[~2026-10-08 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 17:29 [REGRESSION 7.2, BISECTED] KVM: x86: Starting Windows guest triggers UBSAN: array-index-out-of-bounds SimonP
2026-10-07 11:16 ` Paolo Bonzini
2026-10-07 11:18 ` Paolo Bonzini
2026-10-08 15:53 ` SimonP [this message]
2026-10-07 11:47 ` SimonP
2026-10-07 12:05 ` Paolo Bonzini
2026-10-07 12:11 ` SimonP
2026-10-07 14:56 ` Sean Christopherson
2026-10-07 16:08 ` Sean Christopherson
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=ase8Jrg2BBru6lg3@mailbox.org \
--to=simonp.git@mailbox.org \
--cc=kvm@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.