[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DA9TATN3QCAW.3V5G2YL8OV23P@kernel.org>
Date: Fri, 30 May 2025 23:27:14 +0200
From: "Benno Lossin" <lossin@...nel.org>
To: "Christian Schrefl" <chrisi.schrefl@...il.com>, "Danilo Krummrich"
<dakr@...nel.org>, <gregkh@...uxfoundation.org>, <rafael@...nel.org>,
<ojeda@...nel.org>, <alex.gaynor@...il.com>, <boqun.feng@...il.com>,
<gary@...yguo.net>, <bjorn3_gh@...tonmail.com>, <benno.lossin@...ton.me>,
<a.hindborg@...nel.org>, <aliceryhl@...gle.com>, <tmgross@...ch.edu>
Cc: <rust-for-linux@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/7] rust: types: support fallible PinInit types in
Opaque::pin_init
On Fri May 30, 2025 at 10:11 PM CEST, Christian Schrefl wrote:
> On 30.05.25 9:29 PM, Benno Lossin wrote:
>> On Fri May 30, 2025 at 4:24 PM CEST, Danilo Krummrich wrote:
>>> - pub fn pin_init(slot: impl PinInit<T>) -> impl PinInit<Self> {
>>> - Self::ffi_init(|ptr: *mut T| {
>>> + pub fn pin_init<E>(slot: impl PinInit<T, E>) -> impl PinInit<Self, E> {
>>> + Self::try_ffi_init(|ptr: *mut T| -> Result<(), E> {
>>> // SAFETY:
>>> // - `ptr` is a valid pointer to uninitialized memory,
>>> - // - `slot` is not accessed on error; the call is infallible,
>>> + // - `slot` is not accessed on error,
>>> // - `slot` is pinned in memory.
>>> - let _ = unsafe { PinInit::<T>::__pinned_init(slot, ptr) };
>>> + unsafe { PinInit::<T, E>::__pinned_init(slot, ptr) }
>>
>> Could you move this function into an `impl pin_init::Wrapper<T>` block?
>> (it's the same function, but in a trait that was recently added)
>
> This is then basically this patch [0] from my `UnsafePinned` series.
> Just that I did not update the comment. :)
>
> [0]: https://lore.kernel.org/rust-for-linux/20250511-rust_unsafe_pinned-v4-2-a86c32e47e3d@gmail.com/
Oh yeah, I completely forgot we had this... I even reviewed it haha!
---
Cheers,
Benno
Powered by blists - more mailing lists