[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250221051909.37478-1-felipe.contreras@gmail.com>
Date: Thu, 20 Feb 2025 23:19:09 -0600
From: Felipe Contreras <felipe.contreras@...il.com>
To: gregkh@...uxfoundation.org
Cc: airlied@...il.com,
boqun.feng@...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,
Felipe Contreras <felipe.contreras@...il.com>
Subject: Re: Rust kernel policy
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.
> 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?
It *might* help in new stuff.
But since when is the Linux kernel development going for what is better on
paper over what is actually the case? This is wishful thinking.
Remember reiser4 and kdbus? Just because it sounds good on paper doesn't
mean that it will work.
> Adding another language really shouldn't be a problem,
That depends on the specifics of the language and how that language is
developed.
And once again: what *should* be the case and what *is* the case are two
very different things.
--
Felipe Contreras
Powered by blists - more mailing lists