From: syzbot <syzbot+5b59d6d459306a556f54@syzkaller.appspotmail.com>
To: herbert@gondor.apana.org.au, jasowang@redhat.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@dominikbrodowski.net, mpm@selenic.com, mst@redhat.com,
syzkaller-bugs@googlegroups.com, xuanzhuo@linux.alibaba.com,
yuehaibing@huawei.com
Subject: Re: [syzbot] INFO: task hung in add_early_randomness (2)
Date: Tue, 07 Jun 2022 00:30:17 -0700 [thread overview]
Message-ID: <00000000000068486805e0d68f94@google.com> (raw)
In-Reply-To: <000000000000fc128605e08585c6@google.com>
syzbot has bisected this issue to:
commit 8b4ec69d7e098a7ddf832e1e7840de53ed474c77
Author: Jason Wang <jasowang@redhat.com>
Date: Fri May 27 06:01:19 2022 +0000
virtio: harden vring IRQ
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1175c3c7f00000
start commit: f2906aa86338 Linux 5.19-rc1
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1375c3c7f00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1575c3c7f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=cbd131cc02ee620e
dashboard link: https://syzkaller.appspot.com/bug?extid=5b59d6d459306a556f54
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=104f4d4ff00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d6782df00000
Reported-by: syzbot+5b59d6d459306a556f54@syzkaller.appspotmail.com
Fixes: 8b4ec69d7e09 ("virtio: harden vring IRQ")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-06-07 7:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 6:49 [syzbot] INFO: task hung in add_early_randomness (2) syzbot
2022-06-07 1:50 ` syzbot
2022-06-07 7:30 ` syzbot [this message]
2022-06-07 9:05 ` Jason Wang
2022-06-07 10:35 ` Michael S. Tsirkin
2022-06-07 10:53 ` Michael S. Tsirkin
2022-06-08 1:19 ` Jason Wang
2022-06-08 1:37 ` syzbot
2022-06-08 2:35 ` Jason Wang
2022-06-08 2:37 ` syzbot
2022-06-08 2:50 ` Jason Wang
2022-06-08 2:51 ` syzbot
2022-06-08 2:56 ` Jason Wang
2022-06-08 3:15 ` syzbot
2022-06-08 6:07 ` Jason Wang
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=00000000000068486805e0d68f94@google.com \
--to=syzbot+5b59d6d459306a556f54@syzkaller.appspotmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mpm@selenic.com \
--cc=mst@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yuehaibing@huawei.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 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.