linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+25aae26fb74bd5909706@syzkaller.appspotmail.com>,
	herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	linux@dominikbrodowski.net, olivia@selenic.com,
	sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] linux-next boot error: WARNING in kthread_should_stop
Date: Wed, 9 Nov 2022 00:51:03 +0100	[thread overview]
Message-ID: <Y2rrZ8lIIMrKkb2Z@zx2c4.com> (raw)
In-Reply-To: <CACT4Y+a3bJmMf8JNm=SZYOKtgSVnOpY4+bgdT4ugLLhVV-NCEA@mail.gmail.com>

On Tue, Nov 08, 2022 at 02:39:22PM -0800, Dmitry Vyukov wrote:
> On Tue, 8 Nov 2022 at 10:44, 'Jason A. Donenfeld' via syzkaller-bugs
> <syzkaller-bugs@googlegroups.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@zx2c4.com>
> CommitDate: Mon Nov 7 12:47:57 2022 +0100
>     hw_random: use add_hwgenerator_randomness() for early entropy

It's this one: https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git/commit/?id=9807175c5515cea94f8ac6c157f20cc48c40465b

Couple hours more and there'll be a new linux-next with the fix.

Jason

  reply	other threads:[~2022-11-08 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 18:39 [syzbot] linux-next boot error: WARNING in kthread_should_stop syzbot
2022-11-08 18:44 ` Jason A. Donenfeld
2022-11-08 22:39   ` Dmitry Vyukov
2022-11-08 23:51     ` Jason A. Donenfeld [this message]
2022-11-10 21:03       ` 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=Y2rrZ8lIIMrKkb2Z@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=dvyukov@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=olivia@selenic.com \
    --cc=sfr@canb.auug.org.au \
    --cc=syzbot+25aae26fb74bd5909706@syzkaller.appspotmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).