[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z7zYdEM5TkT2LNN1@boqun-archlinux>
Date: Mon, 24 Feb 2025 12:37:08 -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:59:10PM -0600, Felipe Contreras wrote:
> Boqun Feng wrote:
> >
> > 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:
>
> That is a black swan fallacy. Just because you've seen 4 white swans
> that doesn't mean all swans are white.
>
> > , so is there still a question that drivers can be written in Rust?
>
> I didn't say no driver can be written Rust, I questioned whether *all*
> drivers can be written in Rust.
>
Huh? Your previous reply is:
"*If* they can be written in Rust in the first place. You are skipping
that very important precondition."
how does that imply you questioned whether *all* drivers can be written
in Rust.
Care to explain your logic?
Regards,
Boqun
> People are operating under that assumption, but it isn't necessarily true.
>
> --
> Felipe Contreras
Powered by blists - more mailing lists