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: <20250219160740.52ad61d4@gandalf.local.home>
Date: Wed, 19 Feb 2025 16:07:40 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Bart Van Assche <bvanassche@....org>
Cc: Jason Gunthorpe <jgg@...dia.com>, Kees Cook <kees@...nel.org>, Miguel
 Ojeda <miguel.ojeda.sandonis@...il.com>, Christoph Hellwig
 <hch@...radead.org>, 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 Wed, 19 Feb 2025 12:52:14 -0800
Bart Van Assche <bvanassche@....org> wrote:

> On 2/19/25 12:46 PM, Steven Rostedt wrote:
> > I do feel that new drivers written in Rust would help with the
> > vulnerabilities that new drivers usually add to the kernel.  
> 
> For driver developers it is easier to learn C than to learn Rust. I'm
> not sure that all driver developers, especially the "drive by"
> developers, have the skills to learn Rust.

That's a short term problem.

But it's not like we are going to ban C from all new drivers. But as Rust
becomes more popular, we should at the very least make it easy to support
Rust drivers.

-- Steve