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: <DA6BORD02WHT.19D9226XGI6GA@kernel.org>
Date: Mon, 26 May 2025 21:01:06 +0200
From: "Benno Lossin" <lossin@...nel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@...il.com>
Cc: "Miguel Ojeda" <ojeda@...nel.org>, "Alex Gaynor"
 <alex.gaynor@...il.com>, "Boqun Feng" <boqun.feng@...il.com>, "Gary Guo"
 <gary@...yguo.net>, Björn Roy Baron
 <bjorn3_gh@...tonmail.com>, "Andreas Hindborg" <a.hindborg@...nel.org>,
 "Alice Ryhl" <aliceryhl@...gle.com>, "Trevor Gross" <tmgross@...ch.edu>,
 "Danilo Krummrich" <dakr@...nel.org>, "Fiona Behrens" <me@...enk.dev>,
 "Xiangfei Ding" <dingxiangfei2009@...il.com>, <stable@...nel.org>,
 <rust-for-linux@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rust: list: fix path of `assert_pinned!`

On Mon May 26, 2025 at 8:46 PM CEST, Miguel Ojeda wrote:
> On Sun, May 25, 2025 at 7:34 PM Benno Lossin <lossin@...nel.org> wrote:
>>
>> Commit dbd5058ba60c ("rust: make pin-init its own crate") moved all
>> items from pin-init into the pin-init crate, including the
>> `assert_pinned!` macro.
>>
>> Thus fix the path.
>>
>> This occurrence was missed in that commit, since it has no current
>> users, although binder does.
>>
>> Cc: stable@...nel.org # I haven't found the commit in stable yet, but just to be sure.
>> Fixes: dbd5058ba60c ("rust: make pin-init its own crate")
>> Signed-off-by: Benno Lossin <lossin@...nel.org>
>
> Applied to `rust-next` -- thanks!
>
>     [ Reworded slightly as discussed in the list. - Miguel ]
>
> The commit is in v6.15 (rather than just in e.g. rust-next), so it
> should indeed have the Cc: stable (I removed the suffix).

Yes, at the time of writing the commit, I hadn't pulled from Linus'
tree & the stable trees.

Thanks!

---
Cheers,
Benno

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ