linux-kernel - Re: [PATCH] rust: query the compiler for dylib path

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: <CANiq72kM+29COB6vPQPotXqT3acdbrEgdjU2K6FG8gZC0EEhNg@mail.gmail.com>
Date: Wed, 9 Oct 2024 16:20:06 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Tamir Duberstein <tamird@...il.com>
Cc: rust-for-linux@...r.kernel.org, Daniel Gomez <da.gomez@...sung.com>, 
	Fiona Behrens <me@...enk.dev>, Masahiro Yamada <masahiroy@...nel.org>, 
	Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nicolas@...sle.eu>, 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>, 
	"David S. Miller" <davem@...emloft.net>, Kris Van Hees <kris.van.hees@...cle.com>, 
	Íñigo Huguet <ihuguet@...hat.com>, 
	Thomas Weißschuh <linux@...ssschuh.net>, 
	Vegard Nossum <vegard.nossum@...cle.com>, 
	Laurent Pinchart <laurent.pinchart@...asonboard.com>, linux-kernel@...r.kernel.org, 
	linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] rust: query the compiler for dylib path

On Wed, Oct 9, 2024 at 3:18 PM Tamir Duberstein <tamird@...il.com> wrote:
>
> Ah, I see. The relevant discussion took place on zulip[0]. As for policy: I'm
> guessing there isn't one, and the whole endeavor is best-effort.

I am aware of that discussion (it is in our Zulip), but I was
referring to the kernel-wide macOS support, because I had read
Daniel's summary and v2 of that series, and it is not clear to me what
is the latest status on supporting macOS.

In particular, there were some patches NAK'd with arguments that may
apply here (e.g. extra process spawns).

Moreover, how will it get tested going forward? (e.g. currently I
can't, but I could look into setting something up if the kernel wants
to support this). If it breaks, is it considered a bug? etc.

> Thanks Miguel! As this is my first patch, please let me know if further action
> is required.

You're welcome! Yes, a new version would be needed with the proper
tags/authorship, but first we should probably wait to hear what Kbuild
(or the kernel) thinks.

Cheers,
Miguel