[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ziujox51oPzZmwzA@zx2c4.com>
Date: Fri, 26 Apr 2024 14:52: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
Subject: Re: [REGRESSION] Re: [PATCH] Revert "vmgenid: emit uevent when
VMGENID updates"
I don't think adding UAPI to an individual device driver like this is a
good approach especially considering that the virtio changes we
discussed some time ago will likely augment this and create another
means of a similar notification. And given that this intersects with
other userspace-oriented work I hope to get back to pretty soon, I think
introducing some adhoc mechanism like this adds clutter and isn't the
ideal way forward.
On top of that, your extremely aggressive approach and apparent
disregard for established processes and general sneakiness doesn't
really earn you a lot of points here. There wasn't even an iota of
recognition in your reply that you realize the way you've gone about
this is not fine. That doesn't really sit too well, you know?
Powered by blists - more mailing lists