linux-kernel - Re: [RFC PATCH] rust: allow Clang-native `RANDSTRUCT` configs

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: <CANiq72n4Fw96hcuqQeorsfH7z4Tb+R1gdf80H_XkD-oA6z5TSA@mail.gmail.com>
Date: Thu, 9 Jan 2025 15:51:46 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Miguel Ojeda <ojeda@...nel.org>
Cc: Alex Gaynor <alex.gaynor@...il.com>, Nathan Chancellor <nathan@...nel.org>, 
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>, 
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, rust-for-linux@...r.kernel.org, 
	Nick Desaulniers <ndesaulniers@...gle.com>, Bill Wendling <morbo@...gle.com>, 
	Justin Stitt <justinstitt@...gle.com>, llvm@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	patches@...ts.linux.dev, Aaron Ballman <aaron@...onballman.com>, 
	Bill Wendling <isanbard@...il.com>, Cole Nixon <nixontcole@...il.com>, 
	Connor Kuehl <cipkuehl@...il.com>, Fangrui Song <i@...kray.me>, James Foster <jafosterja@...il.com>, 
	Jeff Takahashi <jeffrey.takahashi@...il.com>, Jordan Cantrell <jordan.cantrell@...l.com>, 
	Matthew Maurer <mmaurer@...gle.com>, Nikk Forbus <nicholas.forbus@...il.com>, 
	Qing Zhao <qing.zhao@...cle.com>, Sami Tolvanen <samitolvanen@...gle.com>, 
	Tim Pugh <nwtpugh@...il.com>, Kees Cook <kees@...nel.org>
Subject: Re: [RFC PATCH] rust: allow Clang-native `RANDSTRUCT` configs

On Tue, Nov 19, 2024 at 7:57 PM Miguel Ojeda <ojeda@...nel.org> wrote:
>
> So a patch like this one may just work already, at least in some cases.
> But a fair amount of testing is probably needed for this one, so if you
> have a workload and some time, please give it a go!

I may pick this very early next cycle so that we can get some testing
during the -rc's, and just drop it if something breaks for anyone.

But any other testing beforehand would be still very welcome...

Thanks!

Cheers,
Miguel