Received-SPF: pass (google.com: domain of linux-kernel+bounces-184894-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: Florian Weimer <fweimer@redhat.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org,  patches@lists.linux.dev,  tglx@linutronix.de
Subject: Re: [PATCH v15 2/5] random: add vgetrandom_alloc() syscall
In-Reply-To: <20240521111958.2384173-3-Jason@zx2c4.com> (Jason A. Donenfeld's
	message of "Tue, 21 May 2024 13:18:40 +0200")
References: <20240521111958.2384173-1-Jason@zx2c4.com>
	<20240521111958.2384173-3-Jason@zx2c4.com>
Date: Tue, 21 May 2024 13:48:10 +0200
Message-ID: <87msoj5qth.fsf@oldenburg.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13)
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

* 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 =E2=80=9Cfirst use=E2=80=9D actually means =E2=80=9Cprocesss start=
=E2=80=9D here?  We don't have
a way to report failure from arc4random and similar interfaces.

Thanks,
Florian