Received-SPF: pass (google.com: domain of linux-kernel+bounces-184951-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Tue, 21 May 2024 14:32:20 +0200
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	tglx@linutronix.de, adhemerval.zanella@linaro.org
Subject: Re: [PATCH v15 2/5] random: add vgetrandom_alloc() syscall
Message-ID: <ZkyUVOXzYg7h9OqV@zx2c4.com>
References: <20240521111958.2384173-1-Jason@zx2c4.com>
 <20240521111958.2384173-3-Jason@zx2c4.com>
 <87msoj5qth.fsf@oldenburg.str.redhat.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <87msoj5qth.fsf@oldenburg.str.redhat.com>

On Tue, May 21, 2024 at 01:48:10PM +0200, Florian Weimer wrote:
> * 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.

First use, actually. On failure this just falls back to slow syscall
getrandom() with identical semantics.

Adhemerval has a branch of libc where he implemented this, if you're
interested. He's in CC to send the link.

Jason