linux-kernel - Re: Rust kernel policy

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: <36783d51be7576fcdbf8facc3c94193d78240816.camel@kernel.org>
Date: Tue, 18 Feb 2025 18:35:40 +0200
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Christoph Hellwig <hch@...radead.org>, Miguel Ojeda
	 <miguel.ojeda.sandonis@...il.com>
Cc: rust-for-linux <rust-for-linux@...r.kernel.org>, Linus Torvalds	
 <torvalds@...ux-foundation.org>, Greg KH <gregkh@...uxfoundation.org>,
 David Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
 ksummit@...ts.linux.dev
Subject: Re: Rust kernel policy

On Tue, 2025-02-18 at 08:08 -0800, Christoph Hellwig wrote:
> On Sun, Feb 09, 2025 at 09:56:35PM +0100, Miguel Ojeda wrote:
> > Hi all,
> > 
> > Given the discussions in the last days, I decided to publish this
> > page
> > with what our understanding is:
> > 
> >     https://rust-for-linux.com/rust-kernel-policy
> > 
> > I hope it helps to clarify things. I intend to keep it updated as
> > needed.
> 
> I don't think having a web page in any form is useful.  If you want
> it
> to be valid it has to be in the kernel tree and widely agreed on.

I'd emphasize here that MUST be in the kernel tree. Otherwise, it by the
process can be safely ignored without a second thought.

Doing random pointless annoucements is LF thing, not korg thing ;-)

BR, Jarkko