linux-kernel - Re: [PATCH] rust: kconfig: Don't require RUST_IS

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

Message-ID: <CAK7LNASdG9P90Hnc3M4zK67S_kRtcs5kv8MX7n_B6S5x=FKENw@mail.gmail.com>
Date: Wed, 4 Feb 2026 16:17:26 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>
Cc: Miguel Ojeda <ojeda@...nel.org>, Matthew Maurer <mmaurer@...gle.com>, linux-kbuild@...r.kernel.org, 
	linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH] rust: kconfig: Don't require RUST_IS_AVAILABLE for rustc-option

On Wed, Feb 4, 2026 at 9:16 AM Nathan Chancellor <nathan@...nel.org> wrote:
>
> On Tue, 09 Sep 2025 18:14:20 +0000, Matthew Maurer wrote:
> > The final version of this macro does not fail in the absence of an
> > invokable `$(RUSTC)`, so we don't need to be careful not to invoke it.
> >
> >
>
> Applied to
>
>   https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next
>
> Thanks!
>
> [1/1] rust: kconfig: Don't require RUST_IS_AVAILABLE for rustc-option
>       https://git.kernel.org/kbuild/c/f2445d6f264c6
>
> Please look out for regression or issue reports or other follow up
> comments, as they may result in the patch/series getting dropped or
> reverted. Patches applied to an "unstable" branch are accepted pending
> wider testing in -next and any post-commit review; they will generally
> be moved to the main branch in a week if no issues are found.
>
> Best regards,
> --
> Nathan Chancellor <nathan@...nel.org>
>
>

Removing this comment is correct, but please note
the commit description is not accurate.

Kconfig evaluates all $(shell ...) macros before deciding the
value of RUSAT_IS_AVAILABLE.
You cannot prevent Kconfig from evaluating $(shell ...).
The author of c42297438aee7 did not read
Documentation/kbuild/kconfig-macro-language.rst



--
Best Regards

Masahiro Yamada