linux-kernel - Re: [PATCH v14 0/8] Rust support for mm_struct, vm_area

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: <CANiq72nBx3cRTUC9HWVR8K64Jbq3GCVMss5wuABzra3OLhRUQw@mail.gmail.com>
Date: Thu, 13 Feb 2025 12:32:27 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Alice Ryhl <aliceryhl@...gle.com>, Miguel Ojeda <ojeda@...nel.org>, 
	Matthew Wilcox <willy@...radead.org>, Vlastimil Babka <vbabka@...e.cz>, John Hubbard <jhubbard@...dia.com>, 
	"Liam R. Howlett" <Liam.Howlett@...cle.com>, Andrew Morton <akpm@...ux-foundation.org>, 
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Arnd Bergmann <arnd@...db.de>, Jann Horn <jannh@...gle.com>, 
	Suren Baghdasaryan <surenb@...gle.com>, 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>, 
	Trevor Gross <tmgross@...ch.edu>, linux-kernel@...r.kernel.org, linux-mm@...ck.org, 
	rust-for-linux@...r.kernel.org, Balbir Singh <balbirs@...dia.com>
Subject: Re: [PATCH v14 0/8] Rust support for mm_struct, vm_area_struct, and mmap

On Thu, Feb 13, 2025 at 12:14 PM Lorenzo Stoakes
<lorenzo.stoakes@...cle.com> wrote:
>
> the maintainers for the subsystem generally take series (though of course,
> it is entirely maintained and managed by rust people).

Just in case: I am not sure what "rust people" means here, but if you
meant the Rust subsystem, then it is not the case. Maintenance depends
on what the subsystem wants to do (including how to handle patches,
but also the actual maintenance), who steps up to maintain it, whether
the subsystem wants new co-maintainers or sub-maintainers, etc.

    https://rust-for-linux.com/rust-kernel-policy#how-is-rust-introduced-in-a-subsystem
    https://rust-for-linux.com/rust-kernel-policy#who-maintains-rust-code-in-the-kernel

That is why the cover letter asks about the `MAINTAINERS` file.

I hope that clarifies.

Cheers,
Miguel