From: Danilo Krummrich <dakr@kernel.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: Abdiel Janulgue <abdiel.janulgue@gmail.com>,
rust-for-linux@vger.kernel.org, aliceryhl@google.com,
dakr@redhat.com, linux-kernel@vger.kernel.org,
airlied@redhat.com, miguel.ojeda.sandonis@gmail.com
Subject: Re: [PATCH v2 5/5] rust: firmware: implement `Ownable` for Firmware
Date: Mon, 28 Oct 2024 14:37:06 +0100 [thread overview]
Message-ID: <Zx-Tgm9CJO-Myrgv@pollux> (raw)
In-Reply-To: <Zx68k94GrHb3Kz3-@Boquns-Mac-mini.local>
On Sun, Oct 27, 2024 at 03:20:03PM -0700, Boqun Feng wrote:
> On Wed, Oct 23, 2024 at 11:35:15AM +0200, Danilo Krummrich wrote:
> > On Wed, Oct 23, 2024 at 01:44:49AM +0300, Abdiel Janulgue wrote:
> > > For consistency, wrap the firmware as an `Owned` smart pointer in the
> > > constructor.
> > >
> > > Cc: Danilo Krummrich <dakr@redhat.com>
> > > Suggested-by: Boqun Feng <boqun.feng@gmail.com>
> > > Signed-off-by: Abdiel Janulgue <abdiel.janulgue@gmail.com>
> > > ---
> > > rust/kernel/firmware.rs | 31 ++++++++++++++++++-------------
> > > 1 file changed, 18 insertions(+), 13 deletions(-)
> > >
> > > diff --git a/rust/kernel/firmware.rs b/rust/kernel/firmware.rs
> > > index dee5b4b18aec..6da834b37455 100644
> > > --- a/rust/kernel/firmware.rs
> > > +++ b/rust/kernel/firmware.rs
> > > @@ -4,8 +4,8 @@
> > > //!
> > > //! C header: [`include/linux/firmware.h`](srctree/include/linux/firmware.h)
> > >
> > > -use crate::{bindings, device::Device, error::Error, error::Result, str::CStr};
> > > -use core::ptr::NonNull;
> > > +use crate::{bindings, device::Device, error::Error, error::Result, str::CStr,
> > > + types::{Opaque, Owned, Ownable}};
> > >
> > > /// # Invariants
> > > ///
> > > @@ -52,10 +52,11 @@ fn request_nowarn() -> Self {
> > > /// # Ok(())
> > > /// # }
> > > /// ```
> > > -pub struct Firmware(NonNull<bindings::firmware>);
> > > + #[repr(transparent)]
> > > +pub struct Firmware(Opaque<bindings::firmware>);
> > >
> > > impl Firmware {
> > > - fn request_internal(name: &CStr, dev: &Device, func: FwFunc) -> Result<Self> {
> > > + fn request_internal(name: &CStr, dev: &Device, func: FwFunc) -> Result<Owned<Self>> {
> >
> > I think it's fine to implement this for consistency, but I'm not sure I like
> > that drivers have to refer to it as `Owned<Firmware>`.
> >
>
> May I ask why not? ;-)
I think it's because with this an instance of `Firmware` is never a valid thing
to have, which is a bit weird at a first glance.
But I fully agree with the existance of the `Owned` type and the rationale
below.
>
> Ideally, we should not wrap a pointer to particular type, instead we
> should wrap the type and then combine it with a meaningful pointer type,
> e.g. Box<>, ARef<>, Owned<> ... in this way, we de-couple how the
> lifetime of object is maintained (described by the pointer type) and
> what operations are available on the object (described by the wrapper
> type).
>
> If later on, a firmware object creation is doable in pure Rust code for
> some condition, we can then have a function that returns a
> `KBox<Firmware>` (assume using kmalloc for the object), and it will just
> work (tm).
>
> Regards,
> Boqun
>
> > Anyway, if we keep it this way the patch also needs the following change.
> >
> > diff --git a/rust/kernel/firmware.rs b/rust/kernel/firmware.rs
> > index 6da834b37455..1db854eb2422 100644
> > --- a/rust/kernel/firmware.rs
> > +++ b/rust/kernel/firmware.rs
> > @@ -115,8 +115,8 @@ unsafe fn ptr_drop(ptr: *mut Self) {
> >
> > // SAFETY: `Firmware` only holds a pointer to a C `struct firmware`, which is safe to be used from
> > // any thread.
> > -unsafe impl Send for Firmware {}
> > +unsafe impl Send for Owned<Firmware> {}
> >
> > // SAFETY: `Firmware` only holds a pointer to a C `struct firmware`, references to which are safe to
> > // be used from any thread.
> > -unsafe impl Sync for Firmware {}
> > +unsafe impl Sync for Owned<Firmware> {}
> >
> > > let mut fw: *mut bindings::firmware = core::ptr::null_mut();
> > > let pfw: *mut *mut bindings::firmware = &mut fw;
> > >
> > > @@ -65,25 +66,26 @@ fn request_internal(name: &CStr, dev: &Device, func: FwFunc) -> Result<Self> {
> > > if ret != 0 {
> > > return Err(Error::from_errno(ret));
> > > }
> > > -
> > > + // CAST: Self` is a `repr(transparent)` wrapper around `bindings::firmware`.
> > > + let ptr = fw.cast::<Self>();
> > > // SAFETY: `func` not bailing out with a non-zero error code, guarantees that `fw` is a
> > > // valid pointer to `bindings::firmware`.
> > > - Ok(Firmware(unsafe { NonNull::new_unchecked(fw) }))
> > > + Ok(unsafe { Owned::to_owned(ptr) })
> > > }
> > >
> > > /// Send a firmware request and wait for it. See also `bindings::request_firmware`.
> > > - pub fn request(name: &CStr, dev: &Device) -> Result<Self> {
> > > + pub fn request(name: &CStr, dev: &Device) -> Result<Owned<Self>> {
> > > Self::request_internal(name, dev, FwFunc::request())
> > > }
> > >
> > > /// Send a request for an optional firmware module. See also
> > > /// `bindings::firmware_request_nowarn`.
> > > - pub fn request_nowarn(name: &CStr, dev: &Device) -> Result<Self> {
> > > + pub fn request_nowarn(name: &CStr, dev: &Device) -> Result<Owned<Self>> {
> > > Self::request_internal(name, dev, FwFunc::request_nowarn())
> > > }
> > >
> > > fn as_raw(&self) -> *mut bindings::firmware {
> > > - self.0.as_ptr()
> > > + self.0.get()
> > > }
> > >
> > > /// Returns the size of the requested firmware in bytes.
> > > @@ -101,10 +103,13 @@ pub fn data(&self) -> &[u8] {
> > > }
> > > }
> > >
> > > -impl Drop for Firmware {
> > > - fn drop(&mut self) {
> > > - // SAFETY: `self.as_raw()` is valid by the type invariant.
> > > - unsafe { bindings::release_firmware(self.as_raw()) };
> > > +unsafe impl Ownable for Firmware {
> > > + unsafe fn ptr_drop(ptr: *mut Self) {
> > > + // SAFETY:
> > > + // - By the type invariants, we have ownership of the ptr and can free it.
> > > + // - Per function safety, this is called in Owned::drop(), so `ptr` is a
> > > + // unique pointer to object, it's safe to release the firmware.
> > > + unsafe { bindings::release_firmware(ptr.cast()) };
> > > }
> > > }
> > >
> > > --
> > > 2.43.0
> > >
> >
>
next prev parent reply other threads:[~2024-10-28 13:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 22:44 [PATCH v2 0/5] Introduce Owned type and Ownable trait (was: "rust: page: Add support for vmalloc_to_page") Abdiel Janulgue
2024-10-22 22:44 ` [PATCH v2 1/5] rust: types: add `Owned` type and `Ownable` trait Abdiel Janulgue
2024-10-23 8:10 ` Danilo Krummrich
2024-10-23 9:28 ` Alice Ryhl
2024-10-23 10:26 ` Abdiel Janulgue
2024-10-23 14:58 ` Boqun Feng
2024-10-23 17:52 ` Alice Ryhl
2024-10-23 18:07 ` Boqun Feng
2024-10-24 7:23 ` Alice Ryhl
2024-10-24 7:33 ` Alice Ryhl
2024-11-01 13:38 ` Abdiel Janulgue
2024-11-01 13:49 ` Alice Ryhl
2024-10-22 22:44 ` [PATCH v2 2/5] rust: page: Make ownership of the page pointer explicit Abdiel Janulgue
2024-10-22 22:44 ` [PATCH v2 3/5] rust: page: Extend support to vmalloc_to_page Abdiel Janulgue
2024-10-23 8:42 ` Danilo Krummrich
2024-10-23 9:03 ` Danilo Krummrich
2024-10-23 10:26 ` Abdiel Janulgue
2024-10-23 11:30 ` Danilo Krummrich
2024-10-22 22:44 ` [PATCH v2 4/5] rust: page: Add page_slice_to_page Abdiel Janulgue
2024-10-22 22:44 ` [PATCH v2 5/5] rust: firmware: implement `Ownable` for Firmware Abdiel Janulgue
2024-10-23 9:35 ` Danilo Krummrich
2024-10-23 9:45 ` Danilo Krummrich
2024-10-27 22:20 ` Boqun Feng
2024-10-28 13:37 ` Danilo Krummrich [this message]
2024-10-23 8:03 ` [PATCH v2 0/5] Introduce Owned type and Ownable trait (was: "rust: page: Add support for vmalloc_to_page") Danilo Krummrich
2024-10-23 9:51 ` Miguel Ojeda
2024-10-23 12:01 ` Danilo Krummrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zx-Tgm9CJO-Myrgv@pollux \
--to=dakr@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=airlied@redhat.com \
--cc=aliceryhl@google.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).