From: Peter Zijlstra <peterz@infradead.org>
To: syzbot <syzbot+1f56df64bfb3c29dde6f@syzkaller.appspotmail.com>
Cc: dvhart@infradead.org, hpa@zytor.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
pbonzini@redhat.com, rkrcmar@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: general protection fault in finish_task_switch (2)
Date: Wed, 22 Aug 2018 11:08:23 +0200 [thread overview]
Message-ID: <20180822090823.GT24124@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <0000000000006e87360573f8b328@google.com>
On Tue, Aug 21, 2018 at 02:28:02PM -0700, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: 778a33959a8a Merge tag 'please-pull-noboot' of git://git.k..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=14a5385a400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=214e4990bd49329f
> dashboard link: https://syzkaller.appspot.com/bug?extid=1f56df64bfb3c29dde6f
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> userspace arch: i386
> syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=13ffa561400000
FWIW the lack of whitespace between "repro:" and the URL makes it hard
to copy paste.
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10023961400000
> RIP: 0010:__fire_sched_in_preempt_notifiers kernel/sched/core.c:2481
That repro thing does something dodgy with KVM, which then corrupts the
premption notifier thing. I'm sufficiently KVM clueless to not really
know where to start looking though..
next prev parent reply other threads:[~2018-08-22 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 14:42 general protection fault in finish_task_switch (2) syzbot
2018-08-21 21:28 ` syzbot
2018-08-22 9:08 ` Peter Zijlstra [this message]
2018-08-22 9:22 ` Paolo Bonzini
2018-08-24 20:16 ` Dmitry Vyukov
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=20180822090823.GT24124@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=syzbot+1f56df64bfb3c29dde6f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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).