linux-kernel - Re: [PATCH v7 1/9] rust: Introduce atomic API helpers

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: <CANiq72nCm1-xELn=Z1x1LidKHtjhMtz4FNnakunQ9BqzcS89ew@mail.gmail.com>
Date: Wed, 16 Jul 2025 14:36:27 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Boqun Feng <boqun.feng@...il.com>, linux-kernel@...r.kernel.org, 
	rust-for-linux@...r.kernel.org, lkmm@...ts.linux.dev, 
	linux-arch@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>, 
	Alex Gaynor <alex.gaynor@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>, 
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, 
	Danilo Krummrich <dakr@...nel.org>, Will Deacon <will@...nel.org>, Peter Zijlstra <peterz@...radead.org>, 
	Mark Rutland <mark.rutland@....com>, Wedson Almeida Filho <wedsonaf@...il.com>, 
	Viresh Kumar <viresh.kumar@...aro.org>, Lyude Paul <lyude@...hat.com>, 
	Ingo Molnar <mingo@...nel.org>, Mitchell Levy <levymitchell0@...il.com>, 
	"Paul E. McKenney" <paulmck@...nel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, 
	Thomas Gleixner <tglx@...utronix.de>, Alan Stern <stern@...land.harvard.edu>
Subject: Re: [PATCH v7 1/9] rust: Introduce atomic API helpers

On Wed, Jul 16, 2025 at 11:23 AM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
>
> As this is auto-generated, how do we know when to auto-generate it
> again?  What files does it depend on?  And why can't we just
> auto-generate it at build time instead of having a static file in the
> tree that no one knows when to regenerate it?  :)

If Boqun confirms that there is no reason not to do that, then I can
take a look at that.

Cheers,
Miguel