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: <Z7gQ3kSeCf7gY1i9@Mac.home>
Date: Thu, 20 Feb 2025 21:36:30 -0800
From: Boqun Feng <boqun.feng@...il.com>
To: Felipe Contreras <felipe.contreras@...il.com>
Cc: gregkh@...uxfoundation.org, airlied@...il.com, hch@...radead.org,
	hpa@...or.com, ksummit@...ts.linux.dev,
	linux-kernel@...r.kernel.org, miguel.ojeda.sandonis@...il.com,
	rust-for-linux@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: Rust kernel policy

On Thu, Feb 20, 2025 at 11:19:09PM -0600, Felipe Contreras wrote:
> Greg KH wrote:
> > But for new code / drivers, writing them in rust where these types of
> > bugs just can't happen (or happen much much less) is a win for all of
> > us, why wouldn't we do this?
> 
> *If* they can be written in Rust in the first place. You are skipping that
> very important precondition.
> 

Hmm.. there are multiple old/new drivers (not a complete list) already
in Rust:

* NVME: https://rust-for-linux.com/nvme-driver
* binder: https://rust-for-linux.com/android-binder-driver
* Puzzlefs: https://rust-for-linux.com/puzzlefs-filesystem-driver
* Apple AGX GPU driver: https://rust-for-linux.com/apple-agx-gpu-driver

, so is there still a question that drivers can be written in Rust?

Regards,
Boqun

> > Rust isn't a "silver bullet" that will solve all of our problems, but it
> > sure will help in a huge number of places, so for new stuff going
> > forward, why wouldn't we want that?
> 
[...]