From: syzbot <syzbot+36e93b425cd6eb54fcc1@syzkaller.appspotmail.com>
To: jasowang@redhat.com, kvm@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
michal.lkml@markovi.net, mst@redhat.com, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
virtualization@lists.linux-foundation.org,
yamada.masahiro@socionext.com
Subject: Re: INFO: rcu detected stall in vhost_worker
Date: Fri, 26 Jul 2019 08:26:01 -0700 [thread overview]
Message-ID: <000000000000e87d14058e9728d7@google.com> (raw)
In-Reply-To: <000000000000b4358f058e924c6d@google.com>
syzbot has bisected this bug to:
commit 0ecfebd2b52404ae0c54a878c872bb93363ada36
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Jul 7 22:41:56 2019 +0000
Linux 5.2
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=118810bfa00000
start commit: 13bf6d6a Add linux-next specific files for 20190725
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=8ae987d803395886
dashboard link: https://syzkaller.appspot.com/bug?extid=36e93b425cd6eb54fcc1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15112f3fa00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=131ab578600000
Reported-by: syzbot+36e93b425cd6eb54fcc1@syzkaller.appspotmail.com
Fixes: 0ecfebd2b524 ("Linux 5.2")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-07-26 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 9:38 INFO: rcu detected stall in vhost_worker syzbot
2019-07-26 15:26 ` syzbot [this message]
2019-07-26 21:35 ` Linus Torvalds
2019-07-28 8:36 ` Michael S. Tsirkin
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=000000000000e87d14058e9728d7@google.com \
--to=syzbot+36e93b425cd6eb54fcc1@syzkaller.appspotmail.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=yamada.masahiro@socionext.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).