[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9127c46d-688c-41ea-8f6c-2ca6bdcdd2cd@proton.me>
Date: Sun, 18 Aug 2024 06:01:27 +0000
From: Benno Lossin <benno.lossin@...ton.me>
To: FUJITA Tomonori <fujita.tomonori@...il.com>
Cc: netdev@...r.kernel.org, rust-for-linux@...r.kernel.org, andrew@...n.ch, tmgross@...ch.edu, miguel.ojeda.sandonis@...il.com, aliceryhl@...gle.com
Subject: Re: [PATCH net-next v4 3/6] rust: net::phy implement AsRef<kernel::device::Device> trait
On 18.08.24 04:13, FUJITA Tomonori wrote:
> On Sat, 17 Aug 2024 13:30:15 +0000
> Benno Lossin <benno.lossin@...ton.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
Powered by blists - more mailing lists