linux-kernel - Re: [PATCH] rust: add `rustcheck` make target for check-only builds

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250915103238.3263445e@nimda.home>
Date: Mon, 15 Sep 2025 10:32:38 +0300
From: Onur <work@...rozkan.dev>
To: Andreas Hindborg <a.hindborg@...nel.org>
Cc: rust-for-linux@...r.kernel.org, ojeda@...nel.org, nathan@...nel.org,
 nicolas.schier@...ux.dev, masahiroy@...nel.org, aliceryhl@...gle.com,
 thomas.weissschuh@...utronix.de, tamird@...il.com,
 linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
 alex.gaynor@...il.com, boqun.feng@...il.com, gary@...yguo.net,
 bjorn3_gh@...tonmail.com, lossin@...nel.org, tmgross@...ch.edu,
 dakr@...nel.org
Subject: Re: [PATCH] rust: add `rustcheck` make target for check-only builds

On Sat, 13 Sep 2025 19:46:28 +0200
Andreas Hindborg <a.hindborg@...nel.org> wrote:

> Onur Özkan <work@...rozkan.dev> writes:
> 
> > Adds a new `rustcheck` make target to run a check-only build
> > similar to `cargo check`. This allows us to verify that the Rust
> > sources can build without building/linking final artifacts,
> > which speeds up the iteration (a lot) during development.
> >
> > The target supports the same flags as other Rust build rules, so
> > it can also be used with `CLIPPY=1` (e.g., `make LLVM=1 rustcheck
> > CLIPPY=1) to run Clippy in a faster way.
> >
> > Also, unlike `make LLVM=1`, it doesn't compile large amounts of C
> > code (on a fresh checkout) when the goal is only to check that
> > Rust builds are not broken after some changes.
> >
> 
> I think this is a good idea! However, it looks like this target only
> checks rust code that live in rust/. Can we also check code that lives
> elsewhere, like drivers?
> 

My work depends on the existing build system and that system doesn't
allow me to do that (yet).

Regards,
Onur

> 
> Best regards,
> Andreas Hindborg
> 
>