linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: syzbot <syzbot+42a71c84ef04577f1aef@syzkaller.appspotmail.com>
Cc: dave.hansen@intel.com, hpa@zytor.com, jmattson@google.com,
	joro@8bytes.org, kirill.shutemov@linux.intel.com,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	lstoakes@gmail.com, mingo@redhat.com, pbonzini@redhat.com,
	seanjc@google.com, syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de, vkuznets@redhat.com, wanpengli@tencent.com,
	x86@kernel.org
Subject: Re: general protection fault in vmx_vcpu_run (2)
Date: Wed, 24 Feb 2021 13:27:10 +0100	[thread overview]
Message-ID: <20210224122710.GB20344@zn.tnic> (raw)
In-Reply-To: <00000000000004e7d105bc091e06@google.com>

On Tue, Feb 23, 2021 at 03:17:07PM -0800, syzbot wrote:
> syzbot has bisected this issue to:
> 
> commit 167dcfc08b0b1f964ea95d410aa496fd78adf475
> Author: Lorenzo Stoakes <lstoakes@gmail.com>
> Date:   Tue Dec 15 20:56:41 2020 +0000
> 
>     x86/mm: Increase pgt_buf size for 5-level page tables
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13fe3ea8d00000
> start commit:   a99163e9 Merge tag 'devicetree-for-5.12' of git://git.kern..
> git tree:       upstream
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=10013ea8d00000

No oops here.

> console output: https://syzkaller.appspot.com/x/log.txt?x=17fe3ea8d00000

Nothing special here too.

> kernel config:  https://syzkaller.appspot.com/x/.config?x=49116074dd53b631

Tried this on two boxes, the Intel one doesn't even boot with that
config - and it is pretty standard one - and on the AMD one the
reproducer doesn't trigger anything. It probably won't because the GP
is in vmx_vcpu_run() but since the ioctls were doing something with
IRQCHIP, I thought it is probably vendor-agnostic.

So, all in all, I could use some more info on how you're reproducing and
maybe you could show the oops too.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2021-02-24 12:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 15:20 general protection fault in vmx_vcpu_run (2) syzbot
2021-02-23  8:56 ` syzbot
2021-02-23 23:17 ` syzbot
2021-02-24 12:27   ` Borislav Petkov [this message]
2021-02-24 17:12     ` Dmitry Vyukov
2021-02-24 17:49       ` Borislav Petkov
2021-02-24 18:07         ` Sean Christopherson
2021-02-25 14:16           ` Dmitry Vyukov
2021-02-25 20:25             ` Sean Christopherson
2021-02-25 14:14         ` Dmitry Vyukov
2023-07-10 22:30 ` Sean Christopherson
2023-07-10 22:50   ` [syzbot] [kvm?] " syzbot
2023-07-10 23:39     ` 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=20210224122710.GB20344@zn.tnic \
    --to=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lstoakes@gmail.com \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=syzbot+42a71c84ef04577f1aef@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).