From: cyber security <cs7778503@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Proposal: Introducing Rust for memory-safe Linux kernel components
Date: Mon, 18 Aug 2025 07:43:30 -0400 [thread overview]
Message-ID: <CAPmip_xKv6bA07apqYhyHxTNsnBitVbmcwcYE24xw2RYkDX5oQ@mail.gmail.com> (raw)
I am Security Researcher [RelunSec] so let's talk about rust in linux.
Proposal: Incrementally introduce Rust for select kernel components,
focusing on modules or libraries that benefit from Rust's memory
safety guarantees while maintaining the majority of the kernel in C
for compability reason.
Example: You Can expose Rust driver apis for write kernel driver in
rust and write other component in rust if possible keep using Rust
with C binding example write 60% of C and 43%+ of Rust for compability
reason write some critical part in Rust of kernel so in 2025 for
safety reason you need switch to rust unlike 1997 C is a language
actually 2025/2026 Low Level Language will be Rust.
Experience: I"am Security Researcher. I also started write in rust
some software or even hardware and firmware developement and fix issue
with C bugs via reimplement them in Rust.
Requesting comments and discussion on feasibility, potential pitfalls,
and integration strategy.
Kinds regards
RelunSec
reply other threads:[~2025-08-18 11:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPmip_xKv6bA07apqYhyHxTNsnBitVbmcwcYE24xw2RYkDX5oQ@mail.gmail.com \
--to=cs7778503@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).