linux-kernel - Re: [PATCH 1/7] rust: block: update ARef and AlwaysRefCounted imports from sync::aref

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: <CANiq72=hSTpAj7w8bvcwoJkivxD_FPKnx9jD6iNvhsENnnXBzg@mail.gmail.com>
Date: Sun, 12 Oct 2025 20:01:19 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Shankari Anand <shankari.ak0208@...il.com>
Cc: Andreas Hindborg <a.hindborg@...nel.org>, Jens Axboe <axboe@...nel.dk>, 
	Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, linux-block@...r.kernel.org, 
	rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <lossin@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>, 
	Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>
Subject: Re: [PATCH 1/7] rust: block: update ARef and AlwaysRefCounted imports
 from sync::aref

On Sun, Oct 12, 2025 at 4:05 PM Shankari Anand
<shankari.ak0208@...il.com> wrote:
>
> I'll resend it on top of -rc1.

Yeah, please, thanks! (in v2 I think you say it is on top of
linux-next -- did you mean -rc1?).

> I also noticed that several files have received new commits using
> types::ARef or types::AlwaysRefCounted.
> I wanted to check if it would make sense to update the documentation
> to reflect their new file location.
> Without clear documentation, it might become increasingly difficult
> to remove the re-export as soon as possible, especially as more such commits are added.
>
> Let me know what you think.

I think it is simpler if I apply (even if temporarily) a commit that
moves everything and removes the re-export in linux-next -- that way
people will notice when they try to introduce the code during the
cycle.

Cheers,
Miguel