linux-kernel - Re: [PATCH v2 2/2] rust: sync: clean up LockClassKey and its docs

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: <CAJ-ks9m73KWJc9CuVGd96R2M1OKNAtysEpRGRyBhrV1B8d=kBg@mail.gmail.com>
Date: Tue, 20 Jan 2026 16:05:12 -0500
From: Tamir Duberstein <tamird@...il.com>
To: Boqun Feng <boqun.feng@...il.com>
Cc: Benno Lossin <lossin@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>, 
	Miguel Ojeda <ojeda@...nel.org>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Andreas Hindborg <a.hindborg@...nel.org>, Trevor Gross <tmgross@...ch.edu>, 
	Danilo Krummrich <dakr@...nel.org>, Daniel Almeida <daniel.almeida@...labora.com>, 
	rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] rust: sync: clean up LockClassKey and its docs

On Tue, Aug 12, 2025 at 12:10 PM Boqun Feng <boqun.feng@...il.com> wrote:
>
> On Tue, Aug 12, 2025 at 10:05:55AM +0200, Benno Lossin wrote:
> > On Mon Jul 28, 2025 at 11:42 AM CEST, Alice Ryhl wrote:
> > > Several aspects of the code and documentation for this type is
> > > incomplete. Also several things are hidden from the docs. Thus, clean it
> > > up and make it easier to read the rendered html docs.
> > >
> > > Reviewed-by: Daniel Almeida <daniel.almeida@...labora.com>
> > > Signed-off-by: Alice Ryhl <aliceryhl@...gle.com>
> >
> > Reviewed-by: Benno Lossin <lossin@...nel.org>
> >
>
> Thanks! I'm going to apply your tag for v3 [1], and queue for v6.18.
>
> [1]: https://lore.kernel.org/rust-for-linux/20250811-lock-class-key-cleanup-v3-2-b12967ee1ca2@google.com/

Hey Boqun, looks like this never made it to v6.18, and is instead
headed for v7.0.

This patch introduced an instance of `c_str!("...")` which is
problematic for the c-string migration. Are there any reasonable
options for fixing this before it goes into v7.0?