[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOnCY6TaStZ5ntYKMPQMTUb2ta=NqfxzBKBo2+hxbUX7S-eOiQ@mail.gmail.com>
Date: Mon, 28 Mar 2022 11:34:58 -0700
From: Michael Brooks <m@...etwater.ai>
To: Eric Biggers <ebiggers@...gle.com>
Cc: Sasha Levin <sashal@...nel.org>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, "Jason A. Donenfeld" <Jason@...c4.com>,
"Theodore Ts'o" <tytso@....edu>,
Dominik Brodowski <linux@...inikbrodowski.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jean-Philippe Aumasson <jeanphilippe.aumasson@...il.com>
Subject: Re: [PATCH AUTOSEL 5.17 16/43] random: use computational hash for
entropy extraction
This patch is not ready, but I think it solves the issues Jason has brought up.
-Mike
On Mon, Mar 28, 2022 at 11:08 AM Eric Biggers <ebiggers@...gle.com> wrote:
>
> On Mon, Mar 28, 2022 at 07:18:00AM -0400, Sasha Levin wrote:
> > From: "Jason A. Donenfeld" <Jason@...c4.com>
> >
> > [ Upstream commit 6e8ec2552c7d13991148e551e3325a624d73fac6 ]
> >
>
> I don't think it's a good idea to start backporting random commits to random.c
> that weren't marked for stable. There were a lot of changes in v5.18, and
> sometimes they relate to each other in subtle ways, so the individual commits
> aren't necessarily safe to pick.
>
> IMO, you shouldn't backport any non-stable-Cc'ed commits to random.c unless
> Jason explicitly reviews the exact sequence of commits that you're backporting.
>
> - Eric
Download attachment "keypoolrandom.patch" of type "application/octet-stream" (59858 bytes)
Powered by blists - more mailing lists