linux-kernel - Re: [PATCH] rust: add basic ELF sections parser

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aFq7X_JeZj4n3suo@cassiopeiae>
Date: Tue, 24 Jun 2025 16:51:11 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Alexandre Courbot <acourbot@...dia.com>, Timur Tabi <timur@...nel.org>,
	John Hubbard <jhubbard@...dia.com>, Miguel Ojeda <ojeda@...nel.org>,
	Alex Gaynor <alex.gaynor@...il.com>,
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
	Björn Roy Baron <bjorn3_gh@...tonmail.com>,
	Benno Lossin <benno.lossin@...ton.me>,
	Andreas Hindborg <a.hindborg@...nel.org>,
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
	linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
	airlied@...hat.com
Subject: Re: [PATCH] rust: add basic ELF sections parser

(Cc: +Dave)

On Tue, Jun 24, 2025 at 03:26:11PM +0100, Greg KH wrote:
> We know no user/kernel api can ever be changed in the future, so how can
> we ever accept this?

I think the nova project is a bit special in this aspect, since we develop the
driver upstream for the purpose of breaking the chicken-egg problem of not
getting infrastructure upstream while not having a user, but not getting a user
upstream without having the corresponding infrastructure.

Given that, neither nova-core nor nova-drm make any promises to be working
drivers in the sense of being useful to users.

However, eventually we will hit the point where enough development has been done
such that the drivers actually become useful for users. This will be the turning
point at which we will of course guarantee to keep supporting a firmware version
(or any other uAPI) once introduced.

Until then, it is what the Kconfig claims: "This driver is work in progress and
may not be functional."