From: Linus Torvalds <torvalds@linux-foundation.org>
To: syzbot <syzbot+36e93b425cd6eb54fcc1@syzkaller.appspotmail.com>
Cc: Jason Wang <jasowang@redhat.com>, KVM list <kvm@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
michal.lkml@markovi.net, "Michael S. Tsirkin" <mst@redhat.com>,
Netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
virtualization@lists.linux-foundation.org,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: INFO: rcu detected stall in vhost_worker
Date: Fri, 26 Jul 2019 14:35:25 -0700 [thread overview]
Message-ID: <CAHk-=whnM5+FBJuVoxXELvFgecuc0+vW7ibWy4Gc5qJbW8HL2Q@mail.gmail.com> (raw)
In-Reply-To: <000000000000e87d14058e9728d7@google.com>
On Fri, Jul 26, 2019 at 8:26 AM syzbot
<syzbot+36e93b425cd6eb54fcc1@syzkaller.appspotmail.com> wrote:
>
> 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
That seems very unlikely. That commit literally just changes the
EXTRAVERSION part of the version string.
So even if something actually depended on the version number, even
that wouldn't have triggered any semantic change.
Linus
next prev parent reply other threads:[~2019-07-26 21:35 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
2019-07-26 21:35 ` Linus Torvalds [this message]
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='CAHk-=whnM5+FBJuVoxXELvFgecuc0+vW7ibWy4Gc5qJbW8HL2Q@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--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=syzbot+36e93b425cd6eb54fcc1@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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).