From: Boqun Feng <boqun.feng@gmail.com>
To: Guilherme Giacomo Simoes <trintaeoitogc@gmail.com>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org, ojeda@kernel.org,
alex.gaynor@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, benno.lossin@proton.me,
aliceryhl@google.com, mcgrof@kernel.org, russ.weight@linux.dev,
dakr@redhat.com, a.hindborg@kernel.org,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: device: change the from_raw() function
Date: Mon, 30 Sep 2024 16:22:15 -0700 [thread overview]
Message-ID: <Zvsypwsxi4hMAfOT@boqun-archlinux> (raw)
In-Reply-To: <20240930194637.98260-1-trintaeoitogc@gmail.com>
On Mon, Sep 30, 2024 at 04:46:34PM -0300, Guilherme Giacomo Simoes wrote:
> The function Device::from_raw() increments a refcount by a call to
> bindings::get_device(ptr). This can be confused because usually
> from_raw() functions don't increment a refcount.
> Hence, rename Device::from_raw() to avoid confuion with other "from_raw"
> semantics.
>
> The new name of function should be "get_device" to be consistent with
> the function get_device() already exist in .c files.
>
> This function body also changed, because the `into()` will convert the
> `&'a Device` into `ARef<Device>` and also call `inc_ref` from the
> `AlwaysRefCounted` trait implemented for Device.
>
> Signed-off-by: Guilherme Giacomo Simoes <trintaeoitogc@gmail.com>
This looks really good right now, thanks!
Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
> ---
^^^ note that this is the '---' that Alice mentioned, next time you
could put information that is helpful but you don't want to include in
the commit log here.
Regards,
Boqun
> rust/kernel/device.rs | 15 +++------------
> rust/kernel/firmware.rs | 2 +-
> 2 files changed, 4 insertions(+), 13 deletions(-)
>
> diff --git a/rust/kernel/device.rs b/rust/kernel/device.rs
> index 851018eef885..c8199ee079ef 100644
> --- a/rust/kernel/device.rs
> +++ b/rust/kernel/device.rs
> @@ -51,18 +51,9 @@ impl Device {
> ///
> /// It must also be ensured that `bindings::device::release` can be called from any thread.
> /// While not officially documented, this should be the case for any `struct device`.
> - pub unsafe fn from_raw(ptr: *mut bindings::device) -> ARef<Self> {
> - // SAFETY: By the safety requirements, ptr is valid.
> - // Initially increase the reference count by one to compensate for the final decrement once
> - // this newly created `ARef<Device>` instance is dropped.
> - unsafe { bindings::get_device(ptr) };
> -
> - // CAST: `Self` is a `repr(transparent)` wrapper around `bindings::device`.
> - let ptr = ptr.cast::<Self>();
> -
> - // SAFETY: `ptr` is valid by the safety requirements of this function. By the above call to
> - // `bindings::get_device` we also own a reference to the underlying `struct device`.
> - unsafe { ARef::from_raw(ptr::NonNull::new_unchecked(ptr)) }
> + pub unsafe fn get_device(ptr: *mut bindings::device) -> ARef<Self> {
> + // SAFETY: By the safety requirements ptr is valid
> + unsafe { Self::as_ref(ptr) }.into()
> }
>
> /// Obtain the raw `struct device *`.
> diff --git a/rust/kernel/firmware.rs b/rust/kernel/firmware.rs
> index dee5b4b18aec..13a374a5cdb7 100644
> --- a/rust/kernel/firmware.rs
> +++ b/rust/kernel/firmware.rs
> @@ -44,7 +44,7 @@ fn request_nowarn() -> Self {
> ///
> /// # fn no_run() -> Result<(), Error> {
> /// # // SAFETY: *NOT* safe, just for the example to get an `ARef<Device>` instance
> -/// # let dev = unsafe { Device::from_raw(core::ptr::null_mut()) };
> +/// # let dev = unsafe { Device::get_device(core::ptr::null_mut()) };
> ///
> /// let fw = Firmware::request(c_str!("path/to/firmware.bin"), &dev)?;
> /// let blob = fw.data();
> --
>
> The motivation from this change was will discussion in:
> https://rust-for-linux.zulipchat.com/#narrow/stream/291566-Library/topic/Inconsistency.20of.20.60from_raw.60.2E
>
> I would like to thanks for Greg <gregkh@linuxfoundation.org>, Danilo
> <dakr@kernel.org> and Alice <aliceryhl@google.com> for help me with this
> patch.
>
> 2.46.2
>
next prev parent reply other threads:[~2024-09-30 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 19:46 [PATCH] rust: device: change the from_raw() function Guilherme Giacomo Simoes
2024-09-30 23:22 ` Boqun Feng [this message]
2024-10-01 6:23 ` Greg KH
2024-10-01 11:18 ` Guilherme Giácomo Simões
2024-10-01 12:10 ` Greg KH
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=Zvsypwsxi4hMAfOT@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=dakr@redhat.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=trintaeoitogc@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.