linux-kernel - Re: [PATCH] rust: add `module

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: <2024070924-darkening-knee-bfef@gregkh>
Date: Tue, 9 Jul 2024 10:27:09 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: nmi <nmi@...aspace.dk>
Cc: Luis Chamberlain <mcgrof@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
	rust-for-linux@...r.kernel.org, linux-modules@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Andreas Hindborg <a.hindborg@...sung.com>,
	Adam Bratschi-Kaye <ark.email@...il.com>,
	Sami Tolvanen <samitolvanen@...gle.com>
Subject: Re: [PATCH] rust: add `module_params` macro

On Tue, Jul 09, 2024 at 06:00:46AM +0000, nmi wrote:
> Hi Luis,
> 
> On Monday, July 8th, 2024 at 23:42, Luis Chamberlain <mcgrof@...nel.org> wrote:
> 
> > I'm starting to feel the same way about modules, but modules requires
> > more work than the firmware loader. And since I also know Andreas has
> > already a lot on his plate, I'm at a cross roads. My above request for
> > the firmware loader made sense to the person working on the firmware
> > loader changes, but who would help on the modules side of things? And
> > does this request make sense to help scale?
> >
> > The rationale here is that a rust binding means commitment then also
> > from fresh blood to help co-maintain review C / Rust for exising code
> > when there is will / desire to collaborate from an existing C maintainer.
> >
> > I realize this may be a lot to ask, but I think this is one of the
> > responsible ways to ask to scale here.
> 
> I am not sure I am the right person for the task, because as you say,
> I have a lot on my plate. But perhaps lets schedule a call so I can
> get a sense of the required effort. 

Kernel development is done through emails, not calls :)

If a submitter isn't willing to maintain the code they submit, then it
should be rejected as maintance is the most important part.

Sorry,

greg k-h