From: Alice Ryhl <aliceryhl@google.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: bhelgaas@google.com, gregkh@linuxfoundation.org,
rafael@kernel.org, ojeda@kernel.org, alex.gaynor@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, benno.lossin@proton.me,
a.hindborg@kernel.org, tmgross@umich.edu,
linux-pci@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] rust: device: implement bus_type_raw()
Date: Thu, 20 Mar 2025 13:56:04 +0000 [thread overview]
Message-ID: <Z9wedMSNOntie88F@google.com> (raw)
In-Reply-To: <Z9wDV7Y0-pwe_A-v@pollux>
On Thu, Mar 20, 2025 at 01:00:23PM +0100, Danilo Krummrich wrote:
> On Thu, Mar 20, 2025 at 08:36:02AM +0000, Alice Ryhl wrote:
> > On Wed, Mar 19, 2025 at 09:30:26PM +0100, Danilo Krummrich wrote:
> > > Implement bus_type_raw(), which returns a raw pointer to the device'
> > > struct bus_type.
> > >
> > > This is useful for bus devices, to implement the following trait.
> > >
> > > impl TryFrom<&Device> for &pci::Device
> > >
> > > With this a caller can try to get the bus specific device from a generic
> > > device in a safe way. try_from() will only succeed if the generic
> > > device' bus type pointer matches the pointer of the bus' type.
> > >
> > > Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> > > ---
> > > rust/kernel/device.rs | 7 +++++++
> > > 1 file changed, 7 insertions(+)
> > >
> > > diff --git a/rust/kernel/device.rs b/rust/kernel/device.rs
> > > index 76b341441f3f..e2de0efd4a27 100644
> > > --- a/rust/kernel/device.rs
> > > +++ b/rust/kernel/device.rs
> > > @@ -78,6 +78,13 @@ pub fn parent<'a>(&self) -> Option<&'a Self> {
> > > }
> > > }
> > >
> > > + /// Returns a raw pointer to the device' bus type.
> > > + #[expect(unused)]
> > > + pub(crate) fn bus_type_raw(&self) -> *const bindings::bus_type {
> > > + // SAFETY: By the type invariants, `self.as_raw()` is a valid pointer to a `struct device`.
> >
> > Is this field immutable?
>
> dev->bus is a pointer to a const struct bus_type, yes.
With that added to the SAFETY comment to justify reading the field is
data-race free, you may add:
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
next prev parent reply other threads:[~2025-03-20 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 20:30 [PATCH 0/4] Implement TryFrom<&Device> for bus specific devices Danilo Krummrich
2025-03-19 20:30 ` [PATCH 1/4] rust: device: implement Device::parent() Danilo Krummrich
2025-03-20 8:34 ` Alice Ryhl
2025-03-20 8:40 ` Alice Ryhl
2025-03-20 12:19 ` Danilo Krummrich
2025-03-20 13:56 ` Alice Ryhl
2025-03-19 20:30 ` [PATCH 2/4] rust: device: implement bus_type_raw() Danilo Krummrich
2025-03-20 8:36 ` Alice Ryhl
2025-03-20 12:00 ` Danilo Krummrich
2025-03-20 13:56 ` Alice Ryhl [this message]
2025-03-19 20:30 ` [PATCH 3/4] rust: pci: impl TryFrom<&Device> for &pci::Device Danilo Krummrich
2025-03-20 8:36 ` Alice Ryhl
2025-03-19 20:30 ` [PATCH 4/4] rust: platform: impl TryFrom<&Device> for &platform::Device Danilo Krummrich
2025-03-20 8:37 ` Alice Ryhl
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=Z9wedMSNOntie88F@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@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).