linux-kernel - Re: [PATCH 22/22] MAINTAINERS: add entry for the `pin-init` crate

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: <D87WZI6NPPOG.EJ4OGCTG4O9R@proton.me>
Date: Wed, 05 Mar 2025 00:43:18 +0000
From: Benno Lossin <benno.lossin@...ton.me>
To: Jarkko Sakkinen <jarkko@...nel.org>
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>, Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>, linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH 22/22] MAINTAINERS: add entry for the `pin-init` crate

On Wed Mar 5, 2025 at 1:17 AM CET, Jarkko Sakkinen wrote:
> On Tue, Mar 04, 2025 at 10:56:27PM +0000, Benno Lossin wrote:
>> Add maintainers entry for the `pin-init` crate.
>>
>> This crate is already being maintained by me, but until now there
>> existed two different versions: the version inside of the kernel tree
>> and a user-space version at [1]. The previous patches synchronized these
>> two versions to reduce the maintenance burden. In order to keep them
>> synchronized from now on, separate the maintenance from other Rust code.
>>
>> Link: https://github.com/Rust-for-Linux/pin-init [1]
>> Signed-off-by: Benno Lossin <benno.lossin@...ton.me>
>> ---
>>  MAINTAINERS | 13 +++++++++++++
>>  1 file changed, 13 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 8e0736dc2ee0..ced7fac4dbbe 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -20735,6 +20735,19 @@ S:	Maintained
>>  F:	rust/kernel/alloc.rs
>>  F:	rust/kernel/alloc/
>>
>> +RUST [PIN-INIT]
>
> In some subsystems the order is exactly the opposite. E.g.,
>
> ASIX PHY DRIVER [RUST]

I think that `RUST [PIN-INIT]` makes sense in this case, since it is a
core Rust library. In the example you gave above, the `ASIX PHY DRIVER`
subsystem already exists, so it makes sense to have a rustified version.
With pin-init, there is no C counterpart. So IMO the only other
alternative would be just `PIN-INIT`.

---
Cheers,
Benno

>> +M:	Benno Lossin <benno.lossin@...ton.me>
>> +L:	rust-for-linux@...r.kernel.org
>> +S:	Maintained
>> +W:	https://rust-for-linux.com/pin-init
>> +B:	https://github.com/Rust-for-Linux/pin-init/issues
>> +C:	zulip://rust-for-linux.zulipchat.com
>> +P:	rust/pin-init/CONTRIBUTING.md
>> +T:	git https://github.com/Rust-for-Linux/linux.git pin-init-next
>> +F:	rust/kernel/init.rs
>> +F:	rust/pin-init/
>> +K:	\bpin-init\b|pin_init\b|PinInit
>> +
>>  RXRPC SOCKETS (AF_RXRPC)
>>  M:	David Howells <dhowells@...hat.com>
>>  M:	Marc Dionne <marc.dionne@...istor.com>
>> --
>> 2.47.2
>>
>>
>>
>
> BR, Jarkko