From: Lennart Poettering <mzxreary@0pointer.de>
To: "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
Subject: Re: [PATCH 1/1] vmgenid: emit uevent when VMGENID updates
Date: Tue, 20 Jun 2023 13:28:04 +0200 [thread overview]
Message-ID: <ZJGNREN4tLzQXOJr@gardel-login> (raw)
In-Reply-To: <CAHmME9pVLD-U+iYfv7=HBufRtaSkBmCRpKLH8pbvPNkgozE3cg@mail.gmail.com>
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.
Lennart
--
Lennart Poettering, Berlin
next prev parent reply other threads:[~2023-06-20 11:28 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 [this message]
2023-11-14 12:51 ` Alexander Graf
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=ZJGNREN4tLzQXOJr@gardel-login \
--to=mzxreary@0pointer.de \
--cc=Jason@zx2c4.com \
--cc=bchalios@amazon.es \
--cc=graf@amazon.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.