linux-kernel - Re: Rust kernel policy

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z7bMnpq1cUezsNDl@infradead.org>
Date: Wed, 19 Feb 2025 22:33:02 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Jiri Kosina <jikos@...nel.org>
Cc: Christoph Hellwig <hch@...radead.org>,
	Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
	rust-for-linux <rust-for-linux@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	David Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
	ksummit@...ts.linux.dev
Subject: Re: Rust kernel policy

On Tue, Feb 18, 2025 at 06:36:55PM +0100, Jiri Kosina wrote:
> > [2] The idea of drivers in eBPF as done by HID also really doesn't help
> > with that as much as I like eBPF for some use cases
> 
> I don't necessarily agree on this specific aspect, but what (at least to 
> me personally) is the crucial point here -- if we at some point decide 
> that HID-eBPF is somehow potentially unhealthy for the project / 
> ecosystem, we can just drop it and convert the existing eBPF snippets to a 
> proper simple HID bus drivers trivially (I'd even dare to say that to some 
> extent perhaps programatically).

Well, Linus declared any bpf kfunc / helper program type change that
breaks userspace as a no-go.  And such a change very much does.