From: syzbot <syzbot+681da20be7291be15dca@syzkaller.appspotmail.com>
To: colin.king@canonical.com, f.fangjian@huawei.com,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, lvivier@redhat.com,
mpm@selenic.com, mst@redhat.com, syzkaller-bugs@googlegroups.com,
tangzihao1@hisilicon.com, yuehaibing@huawei.com,
zhangshaokun@hisilicon.com
Subject: Re: [syzbot] INFO: task hung in set_current_rng
Date: Wed, 01 Dec 2021 18:43:12 -0800 [thread overview]
Message-ID: <0000000000006ce3ce05d220c008@google.com> (raw)
In-Reply-To: <000000000000a9ed6205c67e08c6@google.com>
syzbot suspects this issue was fixed by commit:
commit 2bb31abdbe55742c89f4dc0cc26fcbc8467364f6
Author: Laurent Vivier <lvivier@redhat.com>
Date: Thu Oct 28 10:11:09 2021 +0000
hwrng: virtio - don't wait on cleanup
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=171ad129b00000
start commit: 3dbdb38e2869 Merge branch 'for-5.14' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1700b0b2b41cd52c
dashboard link: https://syzkaller.appspot.com/bug?extid=681da20be7291be15dca
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a472e4300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15c51a28300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: hwrng: virtio - don't wait on cleanup
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-12-02 2:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 0:58 [syzbot] INFO: task hung in set_current_rng syzbot
2021-12-02 2:43 ` syzbot [this message]
2021-12-04 9:30 ` 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=0000000000006ce3ce05d220c008@google.com \
--to=syzbot+681da20be7291be15dca@syzkaller.appspotmail.com \
--cc=colin.king@canonical.com \
--cc=f.fangjian@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=mpm@selenic.com \
--cc=mst@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tangzihao1@hisilicon.com \
--cc=yuehaibing@huawei.com \
--cc=zhangshaokun@hisilicon.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.