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: <CANiq72nXN-pkHAG6A19JrjiL-uKpem_-8GN8RhiVgc+sKJN6wA@mail.gmail.com>
Date: Wed, 31 Jul 2024 10:31:58 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Neal Gompa <neal@...pa.dev>
Cc: rust-for-linux@...r.kernel.org, asahi@...ts.linux.dev, 
	linux-kernel@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>, 
	Hector Martin <marcan@...can.st>, Janne Grunau <j@...nau.net>, Asahi Lina <lina@...hilina.net>
Subject: Re: [PATCH] init/Kconfig: Only block on RANDSTRUCT for RUST

On Wed, Jul 31, 2024 at 5:21 AM Neal Gompa <neal@...pa.dev> wrote:
>
> When enabling Rust in the kernel, we only need to block on the
> RANDSTRUCT feature and GCC plugin. The rest of the GCC plugins
> are reasonably safe to enable.

Yeah, only that one is what we had initially years ago, and then we
went the easy route since anyway the mixed builds are best effort at
the moment and GCC plugins could possibly be going away anyway.

Did you test it with the other GCC plugins enabled etc.?

> +       depends on RANDSTRUCT_NONE

Also, why is this changed?

Thanks!

Cheers,
Miguel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ