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: <b6b5tnaw6vnuib7nzcm7ajszxiptqz3i2hex5yengzbsirztks@l3coijkqwtpb>
Date: Thu, 13 Feb 2025 14:46:23 -0500
From: "Liam R. Howlett" <Liam.Howlett@...cle.com>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
        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>,
        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

* Lorenzo Stoakes <lorenzo.stoakes@...cle.com> [250213 07:16]:
> On Thu, Feb 13, 2025 at 01:03:04PM +0100, Miguel Ojeda wrote:
> > On Thu, Feb 13, 2025 at 12:50 PM Lorenzo Stoakes
> > <lorenzo.stoakes@...cle.com> wrote:
> > >
> > > Right, I don't mean the rust subsystem, I mean designated rust
> > > maintainers. The point being that this won't add workload to Andrew, nor
> > > require him nor other mm C people to understand rust.
> >
> > Sounds good, and apologies for being pedantic, but given the recent
> > discussions, I thought I should clarify just in case others read it
> > differently.
> >
> > In the same vein, one more quick thing (that you probably didn't mean
> > in this way, but still, I think it is better I add the note, sorry): I
> > don't think it is true that it will not add workload to Andrew or MM
> > in general. It always adds some workload, even if the maintainers
> > don't handle the patches at all, since they may still need to perform
> > a small change in something Rust related due to another change they
> > need to do, or perhaps at least contact the Rust sub-maintainer to do
> > it for them, etc.
> >
> >     https://rust-for-linux.com/rust-kernel-policy#didnt-you-promise-rust-wouldnt-be-extra-work-for-maintainers
> >
> > Cheers,
> > Miguel
> 
> Ack, for the record I'm happy to help with any work that might come up.

Ack, here too.

Without the drama, I'm not sure how we'd feel so alive :P

Can I be added to whatever list so I can be Cc'ed on the changes on your
side?

Thanks,
Liam


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ