rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 06:01:27 +0000	[thread overview]
Message-ID: <9127c46d-688c-41ea-8f6c-2ca6bdcdd2cd@proton.me> (raw)
In-Reply-To: <20240818.021341.1481957326827323675.fujita.tomonori@gmail.com>

On 18.08.24 04:13, FUJITA Tomonori wrote:
> On Sat, 17 Aug 2024 13:30:15 +0000
> Benno Lossin <benno.lossin@proton.me> wrote:
> 
>>> +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 we may access
>>> +        // this field without additional synchronization.
>>
>> I don't see this invariant on `phy::Device`.
> 
> You meant that `phy::Device` Invariants says that all methods defined
> on this struct are safe to call; not about accessing a field so the
> above SAFETY comment isn't correct, right?

Correct.

>> ---
>> Cheers,
>> Benno
>>
>>> +        unsafe { kernel::device::Device::as_ref(addr_of_mut!((*phydev).mdio.dev)) }
>>> +    }
>>> +}
> 
> SAFETY: A valid `phy_device` always have a valid `mdio.dev`.
> 
> Better?

It would be nice if you could add this on the invariants on
`phy::Device` (you will also have to extend the INVAIRANTS comment that
creates a `&'a mut Device`)

---
Cheers,
Benno


  reply	other threads:[~2024-08-18  6:01 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 [this message]
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
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=9127c46d-688c-41ea-8f6c-2ca6bdcdd2cd@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;
as well as URLs for NNTP newsgroup(s).