From: Gary Guo <gary@kernel.org>
To: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: rust-for-linux@vger.kernel.org
Subject: [RFC PATCH 0/2] Initial klint integration
Date: Tue, 27 Jan 2026 17:11:02 +0000 [thread overview]
Message-ID: <20260127172330.1492107-1-gary@kernel.org> (raw)
From: Gary Guo <gary@garyguo.net>
This RFC series introduce klint integration into the kernel.
Klint is a linting tool (in the form of a custom Rust compiler driver,
similar to how Clippy works) that I have been working on since 2022.
It was initially created to help lint on code that can trigger panics on
allocation failure; this feature has been long obsolete after we started
vendoring alloc crate and subsequently replacing it with a custom
implementation, but over time it also gains some other useful lints.
Lints that are considered ready currently:
* Items available via kernel prelude but imported via other means
* build_error/build_assert calls not being optimized out (klint will
provide you a backtrace to ease analysis, as opposed to just a linker
error).
* Stack frames larger than desired (configured via CONFIG_FRAME_WARN).
The kernel is not currently lint clean. I've already sent out a series
to fix the prelude imports; there is a true-positive with Nova-core's
Cmdq::new method's excessive stack usage which needs fixing.
Many of you may have also heard about klint's ability to perform locking
rule checks, however I did not consider it ready (due to false positives
and inability to analysis some code patterns), so it is not enabled in
the series.
The source code is available at https://github.com/Rust-for-Linux/klint.
It is licensed in "MIT OR Apache-2.0", the same license as the Rust
compiler, as the tool is heavy dependant on the Rust compiler internals.
Currently, there's no pre-compiled binary available; it should be easy
to build for rustup and Nix users; if there are enough demands I can
also consider providing pre-built binaries.
Gary Guo (2):
kbuild: rust: register "klint" as a tool
kbuild: rust: use klint to provide CONFIG_FRAME_WARN
rust/Makefile | 5 ++++-
scripts/Makefile.build | 6 ++++--
scripts/Makefile.warn | 1 +
3 files changed, 9 insertions(+), 3 deletions(-)
base-commit: 615aad0f61e0c7a898184a394dc895c610100d4f
--
2.51.2
next reply other threads:[~2026-01-27 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 17:11 Gary Guo [this message]
2026-01-27 17:11 ` [RFC PATCH 1/2] kbuild: rust: register "klint" as a tool Gary Guo
2026-01-27 17:11 ` [RFC PATCH 2/2] kbuild: rust: use klint to provide CONFIG_FRAME_WARN Gary Guo
2026-01-27 22:15 ` Nathan Chancellor
2026-01-27 22:51 ` Gary Guo
2026-01-27 23:12 ` Miguel Ojeda
2026-01-27 23:27 ` Gary Guo
2026-01-28 0:31 ` Alexandre Courbot
2026-01-28 1:14 ` Gary Guo
2026-01-28 22:02 ` Nathan Chancellor
2026-01-29 0:59 ` Gary Guo
2026-01-30 4:10 ` Nathan Chancellor
2026-01-27 17:35 ` [RFC PATCH 0/2] Initial klint integration Miguel Ojeda
2026-01-27 17:47 ` Danilo Krummrich
2026-01-27 21:26 ` John Hubbard
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=20260127172330.1492107-1-gary@kernel.org \
--to=gary@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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