linux-kernel - Re: [PATCH v4] rust: rbtree: add immutable cursor

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: <CAH5fLgitaTFEhSMm3mZrinsjTktvqLFg6m_JyMxMAd0JzsLtHA@mail.gmail.com>
Date: Mon, 22 Sep 2025 23:17:14 +0200
From: Alice Ryhl <aliceryhl@...gle.com>
To: Vitaly Wool <vitaly.wool@...sulko.se>
Cc: rust-for-linux@...r.kernel.org, Danilo Krummrich <dakr@...nel.org>, 
	Miguel Ojeda <miguel.ojeda.sandonis@...il.com>, linux-kernel@...r.kernel.org, 
	Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>, 
	Gary Guo <gary@...yguo.net>, Bjorn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>, 
	Trevor Gross <tmgross@...ch.edu>, Onur Özkan <work@...rozkan.dev>
Subject: Re: [PATCH v4] rust: rbtree: add immutable cursor

On Mon, Sep 22, 2025 at 2:13 PM Vitaly Wool <vitaly.wool@...sulko.se> wrote:
>
>
>
> On 9/9/25 08:59, Vitaly Wool wrote:
> > Sometimes we may need to iterate over, or find an element in a read
> > only (or read mostly) red-black tree, and in that case we don't need a
> > mutable reference to the tree, which we'll however have to take to be
> > able to use the current (mutable) cursor implementation.
> >
> > This patch adds a simple immutable cursor implementation to RBTree,
> > which enables us to use an immutable tree reference. The existing
> > (fully featured) cursor implementation is renamed to CursorMut,
> > while retaining its functionality.
> >
> > Signed-off-by: Vitaly Wool <vitaly.wool@...sulko.se>
>
> I don't think I've got any feedback on this one, is there anything else
> that needs to be addressed or is this one good to go?

I would like to look, but I'm still tied up in my second consecutive conference.

Alice