linux-kernel - Re: [PATCH v7 10/26] rust: treewide: switch to our kernel `Box` type

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: <ZvlppcutUjuRChPK@pollux>
Date: Sun, 29 Sep 2024 16:52:21 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Gary Guo <gary@...yguo.net>
Cc: ojeda@...nel.org, alex.gaynor@...il.com, wedsonaf@...il.com,
	boqun.feng@...il.com, bjorn3_gh@...tonmail.com,
	benno.lossin@...ton.me, a.hindborg@...sung.com,
	aliceryhl@...gle.com, akpm@...ux-foundation.org,
	daniel.almeida@...labora.com, faith.ekstrand@...labora.com,
	boris.brezillon@...labora.com, lina@...hilina.net,
	mcanal@...lia.com, zhiw@...dia.com, cjia@...dia.com,
	jhubbard@...dia.com, airlied@...hat.com, ajanulgu@...hat.com,
	lyude@...hat.com, linux-kernel@...r.kernel.org,
	rust-for-linux@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v7 10/26] rust: treewide: switch to our kernel `Box` type

On Sat, Sep 28, 2024 at 07:59:13PM +0100, Gary Guo wrote:
> On Thu, 12 Sep 2024 00:52:46 +0200
> Danilo Krummrich <dakr@...nel.org> wrote:
> 
> > Now that we got the kernel `Box` type in place, convert all existing
> > `Box` users to make use of it.
> > 
> > Reviewed-by: Alice Ryhl <aliceryhl@...gle.com>
> > Reviewed-by: Benno Lossin <benno.lossin@...ton.me>
> > Signed-off-by: Danilo Krummrich <dakr@...nel.org>
> 
> Reviewed-by: Gary Guo <gary@...yguo.net>
> 
> Have you considered defaulting the `A` in `Box` to `Kmalloc`? This
> would avoid doing a lot of tree-wide changes.
> 
> If you have a reason against it (I'm pretty sure you have), then
> probably you should put it in the commit message.

Yes, I want people to be forced to make an explicit decision about the allocator
backend they choose, because this has relevant implications.

For instance, it's likely to be unexpected to people coming from userspace Rust,
that (with the default of `Kmalloc`) `Box` allocations larger than
`KMALLOC_MAX_SIZE` would just fail.

> 
> Best,
> Gary
> 
> > ---
> >  drivers/block/rnull.rs            |  4 +--
> >  rust/kernel/init.rs               | 51 ++++++++++++++++---------------
> >  rust/kernel/init/__internal.rs    |  2 +-
> >  rust/kernel/rbtree.rs             | 49 ++++++++++++++++-------------
> >  rust/kernel/sync/arc.rs           | 17 +++++------
> >  rust/kernel/sync/condvar.rs       |  4 +--
> >  rust/kernel/sync/lock/mutex.rs    |  2 +-
> >  rust/kernel/sync/lock/spinlock.rs |  2 +-
> >  rust/kernel/workqueue.rs          | 20 ++++++------
> >  rust/macros/lib.rs                |  6 ++--
> >  10 files changed, 81 insertions(+), 76 deletions(-)
>