linux-kernel - Re: [PATCH 6.14 000/731] 6.14.2-rc1 review

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: <CANiq72nYw+XkHfRZDvS0GceTunxZXqiec2GXeLbPXvPK9OiB8w@mail.gmail.com>
Date: Tue, 8 Apr 2025 18:16:19 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Christian Heusel <christian@...sel.eu>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Thorsten Leemhuis <linux@...mhuis.info>, 
	stable@...r.kernel.org, patches@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org, linux@...ck-us.net, 
	shuah@...nel.org, patches@...nelci.org, lkft-triage@...ts.linaro.org, 
	pavel@...x.de, jonathanh@...dia.com, f.fainelli@...il.com, 
	sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de, 
	conor@...nel.org, hargar@...rosoft.com, broonie@...nel.org, 
	Miguel Ojeda <ojeda@...nel.org>, Justin Forbes <jforbes@...oraproject.org>, 
	Alex Gaynor <alex.gaynor@...il.com>
Subject: Re: [PATCH 6.14 000/731] 6.14.2-rc1 review

On Tue, Apr 8, 2025 at 4:53 PM Christian Heusel <christian@...sel.eu> wrote:
>
> Thanks for pointing this out, I was also missing the relevant
> dependencies in my build system for the rust parts in the kernel to
> actually be built .. IMO it could also hard-error when you specify
> "CONFIG_HAVE_RUST=y" and the tools are missing 🤔

I assume you mean `CONFIG_RUST=y`, i.e. to remove
`CONFIG_RUST_IS_AVAILABLE` and simply request to build with Rust.

And, yeah, it would be simpler and it would prevent the issue of
Kconfig deciding to automatically disable it due to unmet
dependencies. We were asked to do it this way back then, but perhaps
the sentiment has changed now.

What you can do meanwhile is e.g. explicitly check that `CONFIG_RUST`
is `y` after the kernel configuration is saved.

Cheers,
Miguel