linux-kernel - Re: [PATCH v7 07/16] rust: add `io::{Io, IoRaw}` base types

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] [day] [month] [year] [list]

Message-ID: <CANiq72myNPVD=1jHzFxryvnBuwqdw7-PDbPsQ+FdpCjeYtVzig@mail.gmail.com>
Date: Fri, 28 Feb 2025 11:22:33 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Alistair Popple <apopple@...dia.com>
Cc: Danilo Krummrich <dakr@...nel.org>, gregkh@...uxfoundation.org, rafael@...nel.org, 
	bhelgaas@...gle.com, ojeda@...nel.org, alex.gaynor@...il.com, 
	boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com, 
	benno.lossin@...ton.me, tmgross@...ch.edu, a.hindborg@...sung.com, 
	aliceryhl@...gle.com, airlied@...il.com, fujita.tomonori@...il.com, 
	lina@...hilina.net, pstanner@...hat.com, ajanulgu@...hat.com, 
	lyude@...hat.com, robh@...nel.org, daniel.almeida@...labora.com, 
	saravanak@...gle.com, dirk.behme@...bosch.com, j@...nau.net, 
	fabien.parent@...aro.org, chrisi.schrefl@...il.com, paulmck@...nel.org, 
	rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-pci@...r.kernel.org, devicetree@...r.kernel.org, rcu@...r.kernel.org
Subject: Re: [PATCH v7 07/16] rust: add `io::{Io, IoRaw}` base types

On Fri, Feb 28, 2025 at 6:29 AM Alistair Popple <apopple@...dia.com> wrote:
>
> I'm not sure I agree it works perfectly fine. Developer ergonomics are
> an important aspect of any build environment, and I'd argue the ergonomic
> limitation for (2) means it is at least somewhat broken and needs fixing.
>
> Anyway thanks for your time and detailed explainations, I really just started
> this thread as I think reducing friction for existing kernel developers to start
> looking at Rust in the kernel is important.

+1, it is indeed very, very important.

But, just to clarify, we have been caring about ergonomics and
reducing friction for kernel developers since the very beginning,
including asking upstream Rust for features and so on when applicable.

In general, it has been a factor in most topics we have discussed in
the team since 2020, not just for source code or debugging features,
but also docs, KUnit, and so on.

That is why we would like to improve it and why we have it in our
upstream Rust wishlist and so on. In other words, it is not that we do
not see the issue!

I hope that clarifies.

Cheers,
Miguel