linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <graf@amazon.com>
To: Lennart Poettering <mzxreary@0pointer.de>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Babis Chalios <bchalios@amazon.es>, Theodore Ts'o <tytso@mit.edu>,
	<linux-kernel@vger.kernel.org>, <graf@amazon.de>,
	<xmarcalx@amazon.co.uk>, Arnd Bergmann <arnd@arndb.de>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>,
	Ted Tso <tytso@mit.edu>, Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH 1/1] vmgenid: emit uevent when VMGENID updates
Date: Tue, 14 Nov 2023 13:51:59 +0100	[thread overview]
Message-ID: <00d6172f-e291-4e96-9d3e-63ee8e60d556@amazon.com> (raw)
In-Reply-To: <ZJGNREN4tLzQXOJr@gardel-login>

Hi Jason,

On 20.06.23 13:28, Lennart Poettering wrote:
> On Mo, 19.06.23 22:30, Jason A. Donenfeld (Jason@zx2c4.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



  reply	other threads:[~2023-11-14 12:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31  9:51 [PATCH 0/1] User space notifications about VM cloning Babis Chalios
2023-05-31  9:51 ` [PATCH 1/1] vmgenid: emit uevent when VMGENID updates Babis Chalios
2023-06-19  9:14   ` Alexander Graf
2023-06-19 15:48   ` Lennart Poettering
2023-06-19 20:30   ` Jason A. Donenfeld
2023-06-19 20:37     ` Alexander Graf
2023-06-20 10:27     ` Babis Chalios
2023-06-20 11:28     ` Lennart Poettering
2023-11-14 12:51       ` Alexander Graf [this message]
2023-06-16 15:07 ` [PATCH 0/1] User space notifications about VM cloning Babis Chalios
2023-06-28 11:13   ` Alexander Graf
2023-06-28 11:22     ` Greg KH
2023-06-28 11:36       ` Jason A. Donenfeld
2023-06-28 11:47         ` Greg KH
2023-06-28 16:08       ` Greg KH
2023-06-28 16:27     ` Jason A. Donenfeld
2023-06-28 16:53       ` Amit Shah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00d6172f-e291-4e96-9d3e-63ee8e60d556@amazon.com \
    --to=graf@amazon.com \
    --cc=Jason@zx2c4.com \
    --cc=arnd@arndb.de \
    --cc=bchalios@amazon.es \
    --cc=brauner@kernel.org \
    --cc=graf@amazon.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mzxreary@0pointer.de \
    --cc=rostedt@goodmis.org \
    --cc=tytso@mit.edu \
    --cc=xmarcalx@amazon.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).