From: Abdiel Janulgue <abdiel.janulgue@gmail.com>
To: rust-for-linux@vger.kernel.org, aliceryhl@google.com
Cc: dakr@redhat.com, linux-kernel@vger.kernel.org,
airlied@redhat.com, miguel.ojeda.sandonis@gmail.com,
boqun.feng@gmail.com, Abdiel Janulgue <abdiel.janulgue@gmail.com>
Subject: [PATCH v2 5/5] rust: firmware: implement `Ownable` for Firmware
Date: Wed, 23 Oct 2024 01:44:49 +0300 [thread overview]
Message-ID: <20241022224832.1505432-6-abdiel.janulgue@gmail.com> (raw)
In-Reply-To: <20241022224832.1505432-1-abdiel.janulgue@gmail.com>
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>> {
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-22 22:49 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 ` Abdiel Janulgue [this message]
2024-10-23 9:35 ` [PATCH v2 5/5] rust: firmware: implement `Ownable` for Firmware Danilo Krummrich
2024-10-23 9:45 ` Danilo Krummrich
2024-10-27 22:20 ` Boqun Feng
2024-10-28 13:37 ` Danilo Krummrich
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=20241022224832.1505432-6-abdiel.janulgue@gmail.com \
--to=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
all inboxes | Powered by JetHome®