mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Graf <graf@amazon.de>
To: Babis Chalios <bchalios@amazon.es>, Theodore Ts'o <tytso@mit.edu>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	<linux-kernel@vger.kernel.org>
Cc: <mzxreary@0pointer.de>, <xmarcalx@amazon.co.uk>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 1/1] vmgenid: emit uevent when VMGENID updates
Date: Mon, 19 Jun 2023 11:14:06 +0200	[thread overview]
Message-ID: <38b2d1b4-9a26-c6a3-cf8b-af5b3dcf5a9b@amazon.de> (raw)
In-Reply-To: <20230531095119.11202-2-bchalios@amazon.es>


On 31.05.23 11:51, Babis Chalios wrote:
> We receive an ACPI notification every time the VM Generation ID changes
> and use the new ID as fresh randomness added to the entropy pool. This
> commits emits a uevent every time we receive the ACPI notification, as a
> means to notify the user space that it now is in a new VM.
>
> Signed-off-by: Babis Chalios <bchalios@amazon.es>


Thanks Babis! Super simple, yet very effective way to notify system 
software that it may need to adopt to a new environment. I know that the 
systemd folks are super interested in that to for example regenerate 
randomly generated MAC addresses after a clone operation.


Reviewed-by: Alexander Graf <graf@amazon.com>


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-06-19  9:15 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 [this message]
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
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=38b2d1b4-9a26-c6a3-cf8b-af5b3dcf5a9b@amazon.de \
    --to=graf@amazon.de \
    --cc=Jason@zx2c4.com \
    --cc=bchalios@amazon.es \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mzxreary@0pointer.de \
    --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

all inboxes | Powered by JetHome®