linux-kernel - Re: [PATCH] scripts: generate_rust_analyzer.py: add missing macros -> core dep

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: <CANiq72mgYL02C3TUn1q0MK2Yw2OCZC7yW7QNEgB+x9E+BKQHdQ@mail.gmail.com>
Date: Sun, 9 Feb 2025 18:01:29 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Tamir Duberstein <tamird@...il.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, 
	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>, 
	Boris-Chengbiao Zhou <bobo1239@....de>, Fiona Behrens <me@...enk.dev>, Kees Cook <kees@...nel.org>, 
	Wedson Almeida Filho <wedsonaf@...gle.com>, rust-for-linux@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Chayim Refael Friedman <chayimfr@...il.com>, 
	Lukas Wirth <lukas.wirth@...rous-systems.com>, 
	Daniel Almeida <daniel.almeida@...labora.com>
Subject: Re: [PATCH] scripts: generate_rust_analyzer.py: add missing macros ->
 core dep

On Sun, Feb 9, 2025 at 5:39 PM Tamir Duberstein <tamird@...il.com> wrote:
>
> You're right to point out the difference between `kernel::core`
> (module) and `core` (crate). This confusion is solved below (because
> it doesn't actually depend on the `core` crate).

By the way, I didn't read this sentence carefully before: I was not
talking about "`kernel::core` (module)" -- not sure what you mean by
that.

I am talking about the `core` crate in both cases. One is the one we
build for the kernel, and the other is the host one which is used by
proc macros.

The difference may not matter, but one is built differently than the
other, including the `cfg` set differences (and at least the `cfg` set
is used by rust-analyzer).

Moreover, I think it does depend on the `core` crate, at least
indirectly, since `std` depends on `core`.

Cheers,
Miguel