linux-kernel - Re: [PATCH 14/22] rust: add pin-init crate build infrastructure

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] [day] [month] [year] [list]

Message-ID: <D88ENUE2B49N.FGSNLEB107E1@proton.me>
Date: Wed, 05 Mar 2025 14:34:35 +0000
From: Benno Lossin <benno.lossin@...ton.me>
To: Andreas Hindborg <a.hindborg@...nel.org>, Miguel Ojeda <miguel.ojeda.sandonis@...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>, Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>, Masahiro Yamada <masahiroy@...nel.org>, Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nicolas@...sle.eu>, linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH 14/22] rust: add pin-init crate build infrastructure

On Wed Mar 5, 2025 at 3:19 PM CET, Andreas Hindborg wrote:
> "Miguel Ojeda" <miguel.ojeda.sandonis@...il.com> writes:
>
>> On Wed, Mar 5, 2025 at 1:34 PM Andreas Hindborg <a.hindborg@...nel.org> wrote:
>>>
>>> I _really_ think that the ability to run the tests should be present in
>>> the kernel repository. But I also do not want to block this series on it,
>>> if it is something that will be easier to achieve with the build system
>>> overhaul that is in the pipeline.
>>
>> No, that is not the plan. Even with the new build system, this is
>> supposed to be developed upstream as far as I understand, so you will
>> need to run them there anyway.
>>
>> Unless there is a reason we could catch more bugs here, that is.
>
> I guess it would be no different than `syn`. But I think it is a shame
> that we move something that people could contribute to via the kernel
> development flow - out of the kernel development flow.

You *can* send patches via the list, I will pick them up and run them
through the GitHub CI.

Patches that arrive via GitHub will also go through the list and people
can add their tags there.

Also I don't think that pin-init will receive a lot of contributions in
the first place. I do have a lot of changes planned for when we get
`syn`, but other than that, I don't think it will change a lot in the
future.

---
Cheers,
Benno