From: Greg KH <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH stable 5.15.y 0/5] missing random.c-related stable patches
Date: Fri, 3 Jun 2022 16:48:13 +0200 [thread overview]
Message-ID: <YpofLWgbLysxkgb3@kroah.com> (raw)
In-Reply-To: <20220602202327.281510-1-Jason@zx2c4.com>
On Thu, Jun 02, 2022 at 10:23:22PM +0200, Jason A. Donenfeld wrote:
> Hi Greg,
>
> I forgot two things when doing the 5.15 backport. The first is a patch
> from Justin fixing a bug in some of the lib/crypto Kconfig changes,
> which Pablo (CC'd) pointed out was missed. The second is that the
> backport of 5acd35487dc9 ("random: replace custom notifier chain with
> standard one") isn't quite right without Nicolai's patches there too,
> since the drbg module is removable.
>
> I'll continue to monitor all the channels I possibly can for chatter
> about problems, but so far this is all I've run into.
All now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2022-06-03 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 20:23 [PATCH stable 5.15.y 0/5] missing random.c-related stable patches Jason A. Donenfeld
2022-06-02 20:23 ` [PATCH stable 5.15.y 1/5] lib/crypto: add prompts back to crypto libraries Jason A. Donenfeld
2022-06-02 20:23 ` [PATCH stable 5.15.y 2/5] crypto: drbg - prepare for more fine-grained tracking of seeding state Jason A. Donenfeld
2022-06-02 20:23 ` [PATCH stable 5.15.y 3/5] crypto: drbg - track whether DRBG was seeded with !rng_is_initialized() Jason A. Donenfeld
2022-06-02 20:23 ` [PATCH stable 5.15.y 4/5] crypto: drbg - move dynamic ->reseed_threshold adjustments to __drbg_seed() Jason A. Donenfeld
2022-06-02 20:23 ` [PATCH stable 5.15.y 5/5] crypto: drbg - make reseeding from get_random_bytes() synchronous Jason A. Donenfeld
2022-06-03 14:48 ` Greg KH [this message]
2022-06-03 15:14 ` [PATCH stable 5.15.y 0/5] missing random.c-related stable patches Jason A. Donenfeld
2022-06-03 15:23 ` Greg KH
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=YpofLWgbLysxkgb3@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=stable@vger.kernel.org \
/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