[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20f65557-766d-d954-f3ef-c26ad2b661dc@amazon.es>
Date: Fri, 16 Jun 2023 17:07:13 +0200
From: Babis Chalios <bchalios@...zon.es>
To: Theodore Ts'o <tytso@....edu>,
"Jason A. Donenfeld" <Jason@...c4.com>,
<linux-kernel@...r.kernel.org>
CC: <graf@...zon.de>, <mzxreary@...inter.de>, <xmarcalx@...zon.co.uk>,
"Amit Shah" <amit@...nel.org>,
Greg KH <gregkh@...uxfoundation.org>, <bchalios@...zon.es>
Subject: Re: [PATCH 0/1] User space notifications about VM cloning
Hello all,
Some time has passed since I sent this. Any comments/thoughts?
On 31/5/23 11:51, Babis Chalios wrote:
> This patch revisits the story of user space notification about VM
> events. It uses uevents to send a notification to user space that the
> VMGENID has changed, thus we are now in a new VM.
>
> Please note, that this is not a "you need to reseed your PRNGs" event,
> which was what the previous RFC [1] was trying to do. It is, explicitly,
> meant to be a "you are now running in a new VM" event for the user space
> to consume, so it can do things like regenerating its MAC addresses and
> refreshing DHCP. For these cases, we do not want to tie on the "you need
> to reseed your PRNGs" event, since these do not necessarily get emitted
> only when VMs get cloned.
>
> [1] https://lore.kernel.org/lkml/65d872db2e1be29bb03b43ed606e7cc9e74ec08d.camel@infradead.org/T/
>
> Babis Chalios (1):
> vmgenid: emit uevent when VMGENID updates
>
> drivers/virt/vmgenid.c | 2 ++
> 1 file changed, 2 insertions(+)
>
Cheers,
Babis
Powered by blists - more mailing lists