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: <CANiq72=fj0MHiwy5i=FWZxfP_=XsFpjojywF91N6ygdumtQbwQ@mail.gmail.com>
Date: Sun, 26 Jan 2025 21:58:03 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Uros Bizjak <ubizjak@...il.com>, Miguel Ojeda <ojeda@...nel.org>, 
	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org, mm-commits@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] MM updates for 6.14-rc1

On Sun, Jan 26, 2025 at 7:30 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> That seems to be a reasonable assumption. I guess some crazy setup
> *could* install a bindgen that uses a different llvm version than
> rustc itself, but that sounds pretty damn broken.

Tangential to the issue, but a note on this: we have a few warnings in
that `rust_is_available.sh` script for things that "do not look
great", such as bindgen's libclang != Clang when `CC` is Clang, and we
could have a warning for the case you mention, i.e. bindgen's libclang
!= rustc's LLVM.

However, currently some kernel developers use toolchains from upstream
Rust (e.g. from `rustup`) instead of their distributions, so that
could be annoying for them (since their bindgen may be picking
libclang from their distribution).

But eventually when things stabilize more it could make sense, if most
developers stop using those, as a by-default warning.

Cheers,
Miguel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ