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: <CANiq72=p436WBxwebWsEb2Quq0=V4NLMdxRDopM1zrcykk-uzg@mail.gmail.com>
Date: Sat, 22 Feb 2025 13:10:38 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Jarkko Sakkinen <jarkko@...nel.org>
Cc: Fiona Behrens <me@...enk.dev>, Bart Van Assche <bvanassche@....org>, 
	Steven Rostedt <rostedt@...dmis.org>, Jason Gunthorpe <jgg@...dia.com>, Kees Cook <kees@...nel.org>, 
	Christoph Hellwig <hch@...radead.org>, 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 Thu, Feb 20, 2025 at 9:14 AM Jarkko Sakkinen <jarkko@...nel.org> wrote:
>
> The reality of actual kernel development is that you almost never
> compile/run host-to-host, rendering that part of the documentation
> in the battlefield next to useless.
>
> Instead it should have instructions for BuildRoot, Yocto and
> perhaps NixOS (via podman). It should really explain this instead
> of dnf/apt-get etc.

We need to keep the package manager instructions -- there are
developers that use them, and we were explicitly told to add them. So
we cannot remove them.

And, anyway, that documentation is useful to know how to install the
toolchain in other systems/runners/... that use those
packages/containers/binaries.

As for projects like Buildroot, I think it would be ideal to get the
support (or the docs) into them, rather than in the kernel side (plus
I don't see them mentioned in Doc/).

Cheers,
Miguel