From: Sean Christopherson <seanjc@google.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: syzbot <syzbot+a3fcd59df1b372066f5a@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, bp@alien8.de, hpa@zytor.com,
jmattson@google.com, joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mark.rutland@arm.com, masahiroy@kernel.org, mingo@redhat.com,
pbonzini@redhat.com, peterz@infradead.org,
rafael.j.wysocki@intel.com, rostedt@goodmis.org,
sedat.dilek@gmail.com, syzkaller-bugs@googlegroups.com,
vitor@massaru.org, vkuznets@redhat.com, wanpengli@tencent.com,
will@kernel.org, x86@kernel.org
Subject: Re: [syzbot] general protection fault in try_grab_compound_head
Date: Mon, 12 Jul 2021 21:29:00 +0000 [thread overview]
Message-ID: <YOy0HAnhsXJ4W210@google.com> (raw)
In-Reply-To: <87fswpot3i.ffs@nanos.tec.linutronix.de>
On Thu, Jul 08, 2021, Thomas Gleixner wrote:
> On Sat, Jul 03 2021 at 13:24, syzbot wrote:
> > syzbot has bisected this issue to:
> >
> > commit 997acaf6b4b59c6a9c259740312a69ea549cc684
> > Author: Mark Rutland <mark.rutland@arm.com>
> > Date: Mon Jan 11 15:37:07 2021 +0000
> >
> > lockdep: report broken irq restoration
>
> That's the commit which makes the underlying problem visible:
>
> raw_local_irq_restore() called with IRQs enabled
>
> and is triggered by this call chain:
>
> kvm_wait arch/x86/kernel/kvm.c:860 [inline]
> kvm_wait+0xc3/0xe0 arch/x86/kernel/kvm.c:837
And the bug in kvm_wait() was fixed by commit f4e61f0c9add ("x86/kvm: Fix broken
irq restoration in kvm_wait"). The bisection is bad, syzbot happened into the
kvm_wait() WARN and got distracted. The original #GP looks stable, if someone
from mm land has bandwidth.
next prev parent reply other threads:[~2021-07-12 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 15:41 [syzbot] general protection fault in try_grab_compound_head syzbot
2021-07-03 15:41 ` syzbot
2021-07-03 20:24 ` syzbot
2021-07-03 20:24 ` syzbot
2021-07-08 13:03 ` Thomas Gleixner
2021-07-12 21:29 ` Sean Christopherson [this message]
2021-07-13 1:08 ` Joao Martins
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=YOy0HAnhsXJ4W210@google.com \
--to=seanjc@google.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rostedt@goodmis.org \
--cc=sedat.dilek@gmail.com \
--cc=syzbot+a3fcd59df1b372066f5a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vitor@massaru.org \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=will@kernel.org \
--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 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.