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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGSQo03qT=AwJTGSjS+RV1RrpBwMXkkwp-XOWUW5K9LNwbr+WA@mail.gmail.com>
Date: Fri, 23 Jan 2026 09:41:59 -0800
From: Matthew Maurer <mmaurer@...gle.com>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>, 
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, 
	Danilo Krummrich <dakr@...nel.org>, "Theodore Ts'o" <tytso@....edu>, linux-kernel@...r.kernel.org, 
	rust-for-linux@...r.kernel.org, Alexandre Courbot <acourbot@...dia.com>
Subject: Re: [PATCH v5] rust: Add support for feeding entropy to randomness pool

On Thu, Jan 22, 2026 at 3:27 PM Jason A. Donenfeld <Jason@...c4.com> wrote:
>
> On Fri, Jan 02, 2026 at 06:50:16PM +0000, Matthew Maurer wrote:
> > Adds just enough support to allow device drivers to feed entropy to the
> > central pool.
> >
> > Reviewed-by: Alice Ryhl <aliceryhl@...gle.com>
> > Reviewed-by: Alexandre Courbot <acourbot@...dia.com>
> > Signed-off-by: Matthew Maurer <mmaurer@...gle.com>
> > ---
> > This adds bindings for `add_device_randomness` to enable the conversion
> > of `qcom-socinfo` to Rust [1].
> >
> > I'm trying to land it separately because it's much simpler and likely
> > usable by others. The conversation around this code is also likely to be
> > very different than the conversation about the socinfo driver.
>
> Okay, I can take this. But I just wanted to confirm: is that RFC patch
> definitely happening? Should I wait until there's a v1 or something?

I can promise that the patch will be updated (I have a significantly
changed draft locally), but it will still be up to the maintainer
whether it actually lands.

>
> Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ