linux-kernel - Re: [PATCH v15 2/5] random: add vgetrandom

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: <87msoj5qth.fsf@oldenburg.str.redhat.com>
Date: Tue, 21 May 2024 13:48:10 +0200
From: Florian Weimer <fweimer@...hat.com>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: linux-kernel@...r.kernel.org,  patches@...ts.linux.dev,  tglx@...utronix.de
Subject: Re: [PATCH v15 2/5] random: add vgetrandom_alloc() syscall

* Jason A. Donenfeld:

> Libc is expected to allocate a chunk of these on first use, and then
> dole them out to threads as they're created, allocating more when
> needed. The returned address of the first state may be passed to
> munmap(2) with a length of `num * size_per_each`, in order to deallocate
> the memory.

I think “first use” actually means “processs start” here?  We don't have
a way to report failure from arc4random and similar interfaces.

Thanks,
Florian