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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72=OdGRRkxdvSd5bLPkQcfXXFUj4_8LLjVONzpWx5--shw@mail.gmail.com>
Date: Fri, 20 Jun 2025 12:14:36 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Abhinav Ananthu <abhinav.ogl@...il.com>
Cc: vireshk@...nel.org, nm@...com, sboyd@...nel.org, ojeda@...nel.org, 
	alex.gaynor@...il.com, boqun.feng@...il.com, gary@...yguo.net, 
	bjorn3_gh@...tonmail.com, lossin@...nel.org, a.hindborg@...nel.org, 
	aliceryhl@...gle.com, tmgross@...ch.edu, dakr@...nel.org, 
	linux-pm@...r.kernel.org, rust-for-linux@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: [PATCH] rust: opp: use c_* types via kernel prelude

On Fri, Jun 20, 2025 at 12:00 PM Abhinav Ananthu <abhinav.ogl@...il.com> wrote:
>
> Although these types are defined in a crate named `ffi`, they are re-exported
> via the `kernel::prelude` and should be used from there. This aligns with the
> Rust-for-Linux coding guidelines and ensures ABI correctness when interfacing
> with C code.

By the way, thanks for sending these, and please feel free to clean up
the rest -- we have a bunch of instances of this in the tree :)

Happy to create an issue about it.

Cheers,
Miguel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ