From: syzbot <syzbot+c52ab18308964d248092@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [crypto?] INFO: task hung in hwrng_fillfn
Date: Sat, 25 Nov 2023 22:08:04 -0800 [thread overview]
Message-ID: <00000000000037b3e3060b08020f@google.com> (raw)
In-Reply-To: <tencent_0C6106DF136B0364296703BF044A977D1705@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+c52ab18308964d248092@syzkaller.appspotmail.com
Tested on:
commit: 98b1cc82 Linux 6.7-rc2
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=161857af680000
kernel config: https://syzkaller.appspot.com/x/.config?x=6ae1a4ee971a7305
dashboard link: https://syzkaller.appspot.com/bug?extid=c52ab18308964d248092
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=16732694e80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-11-26 6:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_0C6106DF136B0364296703BF044A977D1705@qq.com>
2023-11-26 6:08 ` syzbot [this message]
[not found] <tencent_DB6F26C7B37BA362296123A96443F7759705@qq.com>
2023-11-29 3:23 ` [syzbot] [crypto?] INFO: task hung in hwrng_fillfn syzbot
[not found] <tencent_AEB0786A6F682DF96F6C94A4E8A2EDEACC0A@qq.com>
2023-11-26 4:37 ` syzbot
[not found] <tencent_47250CBA28BB4A33079E2C1B9A4B071BF408@qq.com>
2023-11-26 4:11 ` syzbot
[not found] <tencent_F212DD467B099FAEFC2ECD4C9227CFC6C306@qq.com>
2023-11-26 3:58 ` syzbot
[not found] <20231126015722.882-1-hdanton@sina.com>
2023-11-26 2:20 ` syzbot
2023-11-25 13:21 syzbot
2023-11-26 3:52 ` syzbot
2023-11-26 4:05 ` syzbot
2023-11-26 4:06 ` syzbot
2023-11-26 5:35 ` syzbot
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=00000000000037b3e3060b08020f@google.com \
--to=syzbot+c52ab18308964d248092@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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