From: Alexander Graf <graf@amazon.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Lennart Poettering <mzxreary@0pointer.de>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Babis Chalios <bchalios@amazon.es>, Theodore Ts'o <tytso@mit.edu>,
"Cali, Marco" <xmarcalx@amazon.co.uk>,
Arnd Bergmann <arnd@arndb.de>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
Christian Brauner <brauner@kernel.org>, <linux@leemhuis.info>,
<regressions@lists.linux.dev>,
Paolo Bonzini <pbonzini@redhat.com>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>,
Sean Christopherson <seanjc@google.com>
Subject: Re: [REGRESSION] Re: [PATCH] Revert "vmgenid: emit uevent when VMGENID updates"
Date: Tue, 17 Sep 2024 22:55:20 +0200 [thread overview]
Message-ID: <84c3696d-8108-4a2e-90d7-7830ca6cc3b9@amazon.com> (raw)
In-Reply-To: <CAHmME9rxn5KJJBOC3TqTEgotnsFO5r6F-DJn3ekc5ZgW8OaCFw@mail.gmail.com>
On 17.09.24 20:04, Jason A. Donenfeld wrote:
> On Thu, Jun 13, 2024 at 6:37 PM Alexander Graf <graf@amazon.com> wrote:
>> Friendly ping again. We would really like to have a constructive
>> technical conversation and collaboration on how to make forward progress
>> with VM clone notifications for user space applications that hold unique
>> data and hence need to learn about VM clone events, outside of any
>> randomness semantics.
> With the other work now mostly done, sure, let's pick this up again. I
> think next on the list was getting the virtio rng device delivering VM
> clone events and unique UUIDs. There was a spec change posted a while
> back and a patch for the kernel. Do you want to refresh those? I
> thought that was a promising direction -- and the one we all decided
> together in person as the most viable, race-free way, etc --
> especially because it would make ways of exposing those IDs low cost.
> And, importantly for you, I think that might *also* cover the need
> that you have here, so we'll kill several birds with one stone.
The virtio proposal only addressed consumers that require single atomic
memory updates to learn about any event that is disruptive to their
entropy sources. With vgetrandom and/or rdrand we solved that problem,
so we can close the chapter of that class of use cases.
What is still open are user space applications that require event based
notification on VM clone events - and *only* VM clone events. This
mostly caters for tools like systemd which need to execute policy - such
as generating randomly generated MAC addresses - in the event a VM was
cloned.
That's the use case this patch "vmgenid: emit uevent when VMGENID
updates" is about and I think the best path forward is to just revert
the revert. A uevent from the device driver is a well established, well
fitting Linux mechanism for that type of notification.
Alex
Amazon Web Services Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597
next prev parent reply other threads:[~2024-09-17 20:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 11:48 [PATCH] Revert "vmgenid: emit uevent when VMGENID updates" Jason A. Donenfeld
2024-04-18 12:46 ` Greg Kroah-Hartman
2024-04-22 7:51 ` [REGRESSION] " Alexander Graf
2024-04-23 1:21 ` Jason A. Donenfeld
2024-04-23 6:56 ` Alexander Graf
2024-04-23 12:23 ` Lennart Poettering
2024-04-26 11:33 ` Alexander Graf
2024-04-26 12:52 ` Jason A. Donenfeld
2024-04-26 13:43 ` Babis Chalios
2024-04-26 20:05 ` Alexander Graf
2024-04-29 9:04 ` Lennart Poettering
2024-05-03 10:14 ` Babis Chalios
2024-06-13 16:37 ` Alexander Graf
2024-09-17 18:04 ` Jason A. Donenfeld
2024-09-17 20:55 ` Alexander Graf [this message]
2024-04-26 14:20 ` Linux regression tracking (Thorsten Leemhuis)
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=84c3696d-8108-4a2e-90d7-7830ca6cc3b9@amazon.com \
--to=graf@amazon.com \
--cc=Jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=bchalios@amazon.es \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mikelley@microsoft.com \
--cc=mzxreary@0pointer.de \
--cc=pbonzini@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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