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 19:37:13 -0700 [thread overview]
Message-ID: <0000000000002cccbd05e0e69570@google.com> (raw)
In-Reply-To: <CACGkMEt_e59wRotUo9D1UqubAhe+txy0GF=r1BYBVdND8-uKbA@mail.gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file drivers/char/hw_random/virtio-rng.c
patch: **** unexpected end of file in patch
Tested on:
commit: bd8bb9ae vdpa: ifcvf: set pci driver data in probe
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
dashboard link: https://syzkaller.appspot.com/bug?extid=5b59d6d459306a556f54
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=15f814cff00000
next prev parent reply other threads:[~2022-06-08 4:46 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
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 [this message]
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=0000000000002cccbd05e0e69570@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 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).