linux-kernel - Re: [PATCH] prandom: remove next_pseudo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z6qGtsEdjpz4ETvl@ashyti-mobl2.lan>
Date: Tue, 11 Feb 2025 00:07:34 +0100
From: Andi Shyti <andi.shyti@...ux.intel.com>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: Markus Theil <theil.markus@...il.com>, linux-kernel@...r.kernel.org,
	intel-gfx@...ts.freedesktop.org, netdev@...r.kernel.org,
	tytso@....edu
Subject: Re: [PATCH] prandom: remove next_pseudo_random32

Hi,

On Mon, Feb 10, 2025 at 02:39:43PM +0100, Jason A. Donenfeld wrote:
> Hey Markus,
> 
> Thanks for this. I hadn't realized that next_pseudo_random32() only
> had two users left. Excellent.
> 
> I'll queue this up in the random tree (unless there are objections
> from the maintainers of that test code).

actually would be better if we apply the i915 part in drm-tip
rather than waiting for kernel releases to receive this change in
our branch. It has been source of conflicts and headaches.

May I ask Markus to split the patch in two parts and we handle
the i915 side?

Thanks,
Andi