From: syzbot <syzbot+86c0a866f80d88349f1f@syzkaller.appspotmail.com>
To: ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
hpa@zytor.com, jhs@mojatatu.com, jiri@resnulli.us,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, netdev@vger.kernel.org, pbonzini@redhat.com,
rkrcmar@redhat.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, vladbu@mellanox.com, x86@kernel.org,
xiyou.wangcong@gmail.com
Subject: Re: general protection fault in kvm_pv_send_ipi
Date: Thu, 11 Apr 2019 14:39:01 -0700 [thread overview]
Message-ID: <000000000000ae2c7605864803ff@google.com> (raw)
In-Reply-To: <000000000000a819440574900515@google.com>
syzbot has bisected this bug to:
commit 653cd284a8a857ddfcf24f5bc3bd204a229f6c9f
Author: Vlad Buslov <vladbu@mellanox.com>
Date: Tue Aug 14 18:46:16 2018 +0000
net: sched: always disable bh when taking tcf_lock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16e25dbb200000
start commit: 05193597 Merge branch 'for-4.19' of git://git.kernel.org/p..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=15e25dbb200000
console output: https://syzkaller.appspot.com/x/log.txt?x=11e25dbb200000
kernel config: https://syzkaller.appspot.com/x/.config?x=3b576e333ca31bb2
dashboard link: https://syzkaller.appspot.com/bug?extid=86c0a866f80d88349f1f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137d861e400000
Reported-by: syzbot+86c0a866f80d88349f1f@syzkaller.appspotmail.com
Fixes: 653cd284a8a8 ("net: sched: always disable bh when taking tcf_lock")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-04-11 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 10:00 general protection fault in kvm_pv_send_ipi syzbot
2019-04-11 21:39 ` syzbot [this message]
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=000000000000ae2c7605864803ff@google.com \
--to=syzbot+86c0a866f80d88349f1f@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vladbu@mellanox.com \
--cc=x86@kernel.org \
--cc=xiyou.wangcong@gmail.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 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).