[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <00d6172f-e291-4e96-9d3e-63ee8e60d556@amazon.com>
Date: Tue, 14 Nov 2023 13:51:59 +0100
From: Alexander Graf <graf@...zon.com>
To: Lennart Poettering <mzxreary@...inter.de>,
"Jason A. Donenfeld" <Jason@...c4.com>
CC: Babis Chalios <bchalios@...zon.es>, Theodore Ts'o <tytso@....edu>,
<linux-kernel@...r.kernel.org>, <graf@...zon.de>,
<xmarcalx@...zon.co.uk>, Arnd Bergmann <arnd@...db.de>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
Ted Tso <tytso@....edu>, Christian Brauner <brauner@...nel.org>
Subject: Re: [PATCH 1/1] vmgenid: emit uevent when VMGENID updates
Hi Jason,
On 20.06.23 13:28, Lennart Poettering wrote:
> On Mo, 19.06.23 22:30, Jason A. Donenfeld (Jason@...c4.com) wrote:
>
>> Like the other patch, and as discussed before too, I don't think this
>> has any business being part of (virtual) hardware drivers, and instead
>> belongs in random.c, which might receive these notifications from a
>> variety of devices, and can thus synchronize things accordingly.
>> Please stop posting more of these same approaches. Same nack as the
>> other ones.
> Note the intended usecase for this in userspace really has nothing to
> do with RNGs. We just want an event that is generated when a machine
> is duplicated so that we can request a new DHCP lease, and similar. I
> don't see any relationship to random.c for that.
Checking up on this conversation. The intended use case has nothing to
do with RNG - we merely need a notification for system level user space
that a system clone operation happened so it can act on it.
Please consider taking the patch as is or advise on how to proceed to
address this non-RNG use case.
Thanks,
Alex
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
Powered by blists - more mailing lists