From: Benno Lossin <benno.lossin@proton.me>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
andrew@lunn.ch, tmgross@umich.edu,
miguel.ojeda.sandonis@gmail.com, aliceryhl@google.com
Subject: Re: [PATCH net-next v4 3/6] rust: net::phy implement AsRef<kernel::device::Device> trait
Date: Sun, 18 Aug 2024 15:55:31 +0000 [thread overview]
Message-ID: <3feed4bb-6298-4379-8a71-0b88437b6250@proton.me> (raw)
In-Reply-To: <20240818.112518.2098286584782950755.fujita.tomonori@gmail.com>
On 18.08.24 13:25, FUJITA Tomonori wrote:
> On Sun, 18 Aug 2024 10:42:32 +0000
> Benno Lossin <benno.lossin@proton.me> wrote:
>
>>> /// - Referencing a `phy_device` using this struct asserts that you are in
>>> /// a context where all methods defined on this struct are safe to call.
>>> /// - This struct always has a valid `mdio.dev`.
>>
>> Hmm, I think `self.0.mdio.dev` would be clearer.
>
> Sure, fixed.
>
>>> /// # Safety
>>> ///
>>> /// For the duration of 'a,
>>> /// - the pointer must point at a valid `phy_device`, and the caller
>>> /// must be in a context where all methods defined on this struct
>>> /// are safe to call.
>>> /// - 'mdio.dev' must be a valid.
>>
>> Also here: `(*ptr).mdio.dev`.
>
> Thanks, looks better.
>
> Here's an updated patch.
>
> diff --git a/rust/kernel/net/phy.rs b/rust/kernel/net/phy.rs
> index 5e8137a1972f..ec337cbd391b 100644
> --- a/rust/kernel/net/phy.rs
> +++ b/rust/kernel/net/phy.rs
> @@ -7,8 +7,7 @@
> //! C headers: [`include/linux/phy.h`](srctree/include/linux/phy.h).
>
> use crate::{error::*, prelude::*, types::Opaque};
> -
> -use core::marker::PhantomData;
> +use core::{marker::PhantomData, ptr::addr_of_mut};
>
> /// PHY state machine states.
> ///
> @@ -58,8 +57,9 @@ pub enum DuplexMode {
> ///
> /// # Invariants
> ///
> -/// Referencing a `phy_device` using this struct asserts that you are in
> -/// a context where all methods defined on this struct are safe to call.
> +/// - Referencing a `phy_device` using this struct asserts that you are in
> +/// a context where all methods defined on this struct are safe to call.
> +/// - This struct always has a valid `self.0.mdio.dev`.
> ///
> /// [`struct phy_device`]: srctree/include/linux/phy.h
> // During the calls to most functions in [`Driver`], the C side (`PHYLIB`) holds a lock that is
> @@ -76,9 +76,11 @@ impl Device {
> ///
> /// # Safety
> ///
> - /// For the duration of 'a, the pointer must point at a valid `phy_device`,
> - /// and the caller must be in a context where all methods defined on this struct
> - /// are safe to call.
> + /// For the duration of 'a,
> + /// - the pointer must point at a valid `phy_device`, and the caller
> + /// must be in a context where all methods defined on this struct
> + /// are safe to call.
> + /// - `(*ptr).mdio.dev` must be a valid.
> unsafe fn from_raw<'a>(ptr: *mut bindings::phy_device) -> &'a mut Self {
> // CAST: `Self` is a `repr(transparent)` wrapper around `bindings::phy_device`.
> let ptr = ptr.cast::<Self>();
> @@ -302,6 +304,14 @@ pub fn genphy_read_abilities(&mut self) -> Result {
> }
> }
>
> +impl AsRef<kernel::device::Device> for Device {
> + fn as_ref(&self) -> &kernel::device::Device {
> + let phydev = self.0.get();
> + // SAFETY: The struct invariant ensures that `mdio.dev` is valid.
> + unsafe { kernel::device::Device::as_ref(addr_of_mut!((*phydev).mdio.dev)) }
> + }
> +}
> +
> /// Defines certain other features this PHY supports (like interrupts).
> ///
> /// These flag values are used in [`Driver::FLAGS`].
> --
> 2.34.1
>
This looks, good, if you want, you can add my reviewed-by on this patch.
---
Cheers,
Benno
next prev parent reply other threads:[~2024-08-18 15:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 5:19 [PATCH net-next v4 0/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-08-17 5:19 ` [PATCH net-next v4 1/6] rust: sizes: add commonly used constants FUJITA Tomonori
2024-08-17 5:53 ` Benno Lossin
2024-08-17 5:19 ` [PATCH net-next v4 2/6] rust: net::phy support probe callback FUJITA Tomonori
2024-08-17 5:59 ` Benno Lossin
2024-08-17 5:19 ` [PATCH net-next v4 3/6] rust: net::phy implement AsRef<kernel::device::Device> trait FUJITA Tomonori
2024-08-17 13:30 ` Benno Lossin
2024-08-18 2:13 ` FUJITA Tomonori
2024-08-18 6:01 ` Benno Lossin
2024-08-18 7:36 ` FUJITA Tomonori
2024-08-18 9:03 ` Benno Lossin
2024-08-18 9:15 ` FUJITA Tomonori
2024-08-18 10:42 ` Benno Lossin
2024-08-18 11:25 ` FUJITA Tomonori
2024-08-18 15:55 ` Benno Lossin [this message]
2024-08-18 15:38 ` Andrew Lunn
2024-08-18 15:45 ` Greg KH
2024-08-18 15:54 ` Benno Lossin
2024-08-18 16:16 ` Andrew Lunn
2024-08-18 16:19 ` Benno Lossin
2024-08-17 5:19 ` [PATCH net-next v4 4/6] rust: net::phy unified read/write API for C22 and C45 registers FUJITA Tomonori
2024-08-17 18:43 ` Andrew Lunn
2024-08-17 5:19 ` [PATCH net-next v4 5/6] rust: net::phy unified genphy_read_status function " FUJITA Tomonori
2024-08-17 18:44 ` Andrew Lunn
2024-08-17 5:19 ` [PATCH net-next v4 6/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-08-17 18:51 ` Andrew Lunn
2024-08-17 21:34 ` Benno Lossin
2024-08-18 15:44 ` Andrew Lunn
2024-08-18 16:16 ` Benno Lossin
2024-08-18 17:39 ` Andrew Lunn
2024-08-19 0:22 ` Miguel Ojeda
2024-08-18 16:10 ` Benno Lossin
2024-08-18 23:38 ` FUJITA Tomonori
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=3feed4bb-6298-4379-8a71-0b88437b6250@proton.me \
--to=benno.lossin@proton.me \
--cc=aliceryhl@google.com \
--cc=andrew@lunn.ch \
--cc=fujita.tomonori@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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