[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9rxn5KJJBOC3TqTEgotnsFO5r6F-DJn3ekc5ZgW8OaCFw@mail.gmail.com>
Date: Tue, 17 Sep 2024 20:04:51 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Alexander Graf <graf@...zon.com>
Cc: Lennart Poettering <mzxreary@...inter.de>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>, Babis Chalios <bchalios@...zon.es>,
"Theodore Ts'o" <tytso@....edu>, "Cali, Marco" <xmarcalx@...zon.co.uk>, Arnd Bergmann <arnd@...db.de>,
"rostedt@...dmis.org" <rostedt@...dmis.org>, Christian Brauner <brauner@...nel.org>, linux@...mhuis.info,
regressions@...ts.linux.dev, Paolo Bonzini <pbonzini@...hat.com>,
"Michael Kelley (LINUX)" <mikelley@...rosoft.com>, Sean Christopherson <seanjc@...gle.com>
Subject: Re: [REGRESSION] Re: [PATCH] Revert "vmgenid: emit uevent when
VMGENID updates"
On Thu, Jun 13, 2024 at 6:37 PM Alexander Graf <graf@...zon.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.
Jason
Powered by blists - more mailing lists