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>] [day] [month] [year] [list]
Message-ID: <CAFf+5zgwEJ_Rzv9GM0yPSaRTXw+w15NgGK1CWj5zjDW+DZ03kA@mail.gmail.com>
Date: Fri, 21 Mar 2025 18:33:52 +0530
From: Amit <amitchoudhary0523@...il.com>
To: linux-kernel@...r.kernel.org
Subject: Some concerns about allowing Rust code in linux kernel.

Hi,

I have some concerns regarding Rust code in linux kernel.

Many C programmers who contribute to linux kernel and maintain the
kernel may not want to learn Rust. I have contributed few patches to
linux kernel a long time ago and I also don't want to learn Rust.

So, what are the chances that 10 years down the line, we will still
have Rust contributors/maintainers for linux kernel?

What if Rust kernel developers abandon linux kernel 5 years down the line?

There are tons of C programmers around and they will be around because
OS/Networking software is written in C and will keep getting written
in C.

What is the guarantee that we will have tons of Rust programmers down the line?

Java developers are not going to learn Rust.

Only C/C++ developers may want to learn Rust but then the question is
how many C/C++ developers would want to learn and become an expert in
a new language? And then how many of those will actually contribute to
linux kernel?

I am not suggesting anything. I just had these concerns, so I wrote them here.

Regards,
Amit

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ