[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+a3bJmMf8JNm=SZYOKtgSVnOpY4+bgdT4ugLLhVV-NCEA@mail.gmail.com>
Date: Tue, 8 Nov 2022 14:39:22 -0800
From: Dmitry Vyukov <dvyukov@...gle.com>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: syzbot <syzbot+25aae26fb74bd5909706@...kaller.appspotmail.com>,
herbert@...dor.apana.org.au, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
linux@...inikbrodowski.net, olivia@...enic.com,
sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] linux-next boot error: WARNING in kthread_should_stop
On Tue, 8 Nov 2022 at 10:44, 'Jason A. Donenfeld' via syzkaller-bugs
<syzkaller-bugs@...glegroups.com> wrote:
>
> Already fixed in the tree.
Hi Jason,
The latest commit touching this code in linux-next is this one. Is it
the fixing commit?
commit e0a37003ff0beed62e85a00e313b21764c5f1d4f
Author: Jason A. Donenfeld <Jason@...c4.com>
CommitDate: Mon Nov 7 12:47:57 2022 +0100
hw_random: use add_hwgenerator_randomness() for early entropy
Powered by blists - more mailing lists