From: Sean Christopherson <seanjc@google.com>
To: Jinpu Wang <jinpu.wang@ionos.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
kvm@vger.kernel.org
Subject: Re: 5.10.131-rc1 crash with int3: RIP 0010:xaddw_ax_dx+0x9/0x10 [kvm]
Date: Wed, 13 Jul 2022 21:11:34 +0000 [thread overview]
Message-ID: <Ys81Bor99YlUrM0k@google.com> (raw)
In-Reply-To: <CAMGffEmdqz-ggqkHOwddu7bTPBs47tY-5cSi58qvYwPmxrYumg@mail.gmail.com>
On Wed, Jul 13, 2022, Jinpu Wang wrote:
> On Wed, Jul 13, 2022 at 3:01 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Jul 13, 2022 at 02:26:44PM +0200, Jinpu Wang wrote:
> > > On Wed, Jul 13, 2022 at 12:49 PM Jinpu Wang <jinpu.wang@ionos.com> wrote:
> > > > #5.10.131-1+feature+linux+5.10.y+20220712.1850+30f4172c~deb11
...
> > > > [ 1895.979325] Call Trace:
> > > > [ 1895.979325] ? fastop+0x59/0xa0 [kvm]
> > > > [ 1895.979326] ? x86_emulate_insn+0x73a/0xe00 [kvm]
> > > > [ 1895.979326] ? x86_emulate_instruction+0x2d0/0x750 [kvm]
> > > > [ 1895.979326] ? vmx_vcpu_load+0x21/0x70 [kvm_intel]
> > > > [ 1895.979327] ? complete_emulated_mmio+0x236/0x310 [kvm]
> > > > [ 1895.979327] ? kvm_arch_vcpu_ioctl_run+0x1744/0x1920 [kvm]
> > > > [ 1895.979327] ? kvm_vcpu_ioctl+0x211/0x5a0 [kvm]
> > > > [ 1895.979328] ? __fget_files+0x79/0xb0
> > > > [ 1895.979328] ? __fget_files+0x79/0xb0
> > > > [ 1895.979328] ? __x64_sys_ioctl+0x8b/0xc0
> > > > [ 1895.979329] ? do_syscall_64+0x33/0x40
> > > > [ 1895.979329] ? entry_SYSCALL_64_after_hwframe+0x61/0xc6
...
> > > > Is this bug known, any hint how to fix it?
> > > I did more tests on different Servers, so far all the machine
> > > checked(Skylake/Icelake/Haswell/Broadwell/EPYC) crash immediately
> > > except AMD Opteron.
> > > kvm-unit-tests succeeded without regression.
> >
> > Same issue on Linus's tree right now as well? Or does that pass just
> > fine?
>
> Hi Greg,
>
> I haven't try linus tree, but just tried 5.15.55-rc1 on Intel Skylake,
> it crashed the same.
>
> I will give Linus tree a try.
Looks like fastop() got broken by the retbleed mitigations, i.e. this isn't unique
to stable trees.
https://lore.kernel.org/all/20220713171241.184026-1-cascardo@canonical.com
next prev parent reply other threads:[~2022-07-13 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 10:49 5.10.131-rc1 crash with int3: RIP 0010:xaddw_ax_dx+0x9/0x10 [kvm] Jinpu Wang
2022-07-13 12:26 ` Jinpu Wang
2022-07-13 13:01 ` Greg Kroah-Hartman
2022-07-13 13:18 ` Jinpu Wang
2022-07-13 21:11 ` Sean Christopherson [this message]
2022-07-14 7:16 ` Jinpu Wang
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=Ys81Bor99YlUrM0k@google.com \
--to=seanjc@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jinpu.wang@ionos.com \
--cc=kvm@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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