From: Christian Schrefl <chrisi.schrefl@gmail.com>
To: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Lee Jones" <lee@kernel.org>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] rust: miscdevice: Add additional data to MiscDeviceRegistration
Date: Fri, 24 Jan 2025 00:26:35 +0100 [thread overview]
Message-ID: <8953765e-d978-4a91-bc81-9ab154ac2255@gmail.com> (raw)
In-Reply-To: <20250119-b4-rust_miscdevice_registrationdata-v1-2-edbf18dde5fc@gmail.com>
On 19.01.25 11:11 PM, Christian Schrefl wrote:
> When using the Rust miscdevice bindings, you generally embed the
> MiscDeviceRegistration within another struct:
>
> struct MyDriverData {
> data: SomeOtherData,
> misc: MiscDeviceRegistration<MyMiscFile>
> }
>
> <snip>
>
> impl<T: MiscDevice> MiscDeviceRegistration<T> {
> /// Register a misc device.
> - pub fn register(opts: MiscDeviceOptions) -> impl PinInit<Self, Error> {
> + pub fn register(
> + opts: MiscDeviceOptions,
> + data: impl PinInit<T::RegistrationData, Error>,
> + ) -> impl PinInit<Self, Error> {
> try_pin_init!(Self {
> inner <- Opaque::try_ffi_init(move |slot: *mut bindings::miscdevice| {
> // SAFETY: The initializer can write to the provided `slot`.
> @@ -79,6 +85,7 @@ pub fn register(opts: MiscDeviceOptions) -> impl PinInit<Self, Error> {
> // misc device.
> to_result(unsafe { bindings::misc_register(slot) })
> }),
> + data <- Aliased::try_pin_init(data),
> _t: PhantomData,
> })
After some thought I think `register` needs to be something like:
pub fn register(
opts: MiscDeviceOptions,
data: impl PinInit<T::RegistrationData, Error>,
) -> impl PinInit<Self, Error> {
try_pin_init!(Self {
inner <- Opaque::try_ffi_init(move |slot: *mut bindings::miscdevice| {
// SAFETY: The initializer can write to the provided `slot`.
unsafe { slot.write(opts.into_raw::<T>()) };
Ok::<(), Error>(())
}),
data <- UnsafePinned::try_pin_init(data),
_t: PhantomData,
})
.pin_chain(|slot| {
// SAFETY: We just wrote the misc device options to the slot. The miscdevice will
// get unregistered before `slot` is deallocated because the memory is pinned and
// the destructor of this type deallocates the memory.
// `data` is Initialized before `misc_register` so no race with `fops->open()`
// is possible.
// INVARIANT: If this returns `Ok(())`, then the `slot` will contain a registered
// misc device.
to_result(unsafe { bindings::misc_register(slot.as_raw()) }).map_err(|err| {
// Drop the Data in case misc_register fails.
// SAFETY:
// - We just initialized `data`.
// - We are about to return `Err(err)`, so it is valid for us to drop `data`.
unsafe {
ptr::drop_in_place(slot.data.get());
}
err
})
})
}
to make sure that `misc_register` is called after data is initialized and to that
`data` will be dropped correctly in case `misc_register` fails.
But I'm not very familiar with `(try_)pin_init!` so this might be unnecessary?
> }
> @@ -97,10 +104,18 @@ pub fn device(&self) -> &Device {
> // before the underlying `struct miscdevice` is destroyed.
> unsafe { Device::as_ref((*self.as_raw()).this_device) }
> }
> +
> + /// Access the additional data stored in this registration.
> + pub fn data(&self) -> &T::RegistrationData {
> + // SAFETY:
> + // No mutable reference to the value contained by self.data can ever be created.
> + // The value contained by self.data is valid for the entire lifetime of self.
> + unsafe { &*self.data.get() }
> + }
> }
>
> #[pinned_drop]
> -impl<T> PinnedDrop for MiscDeviceRegistration<T> {
> +impl<T: MiscDevice> PinnedDrop for MiscDeviceRegistration<T> {
> fn drop(self: Pin<&mut Self>) {
> // SAFETY: We know that the device is registered by the type invariants.
> unsafe { bindings::misc_deregister(self.inner.get()) };
> @@ -113,6 +128,11 @@ pub trait MiscDevice: Sized {
> /// What kind of pointer should `Self` be wrapped in.
> type Ptr: ForeignOwnable + Send + Sync;
>
> + /// The additional data carried by the `MiscDeviceRegistration` for this `MiscDevice`.
> + /// If no additional data is required than () should be used.
> + /// This data can be accessed in `open()` using `MiscDeviceRegistration::data()`.
> + type RegistrationData: Sync;
> +
> /// Called when the misc device is opened.
> ///
> /// The returned pointer will be stored as the private data for the file.
> @@ -218,6 +238,9 @@ impl<T: MiscDevice> VtableHelper<T> {
> // SAFETY: This is a miscdevice, so `misc_open()` set the private data to a pointer to the
> // associated `struct miscdevice` before calling into this method. Furthermore, `misc_open()`
> // ensures that the miscdevice can't be unregistered and freed during this call to `fops_open`.
> + // Since this the `MiscDeviceRegistration` struct uses `#[repr(C)]` and the miscdevice is the
> + // first entry it is guaranteed that the address of the miscdevice is the same as the address
> + // of the entire `MiscDeviceRegistration` struct.
> let misc = unsafe { &*misc_ptr.cast::<MiscDeviceRegistration<T>>() };
>
> // SAFETY:
> diff --git a/samples/rust/rust_misc_device.rs b/samples/rust/rust_misc_device.rs
> index 40ad7266c2252e5c0b4e91e501ef9ada2eda3b16..779fcfd64119bdd5b4f8be740f7e8336c652b4d3 100644
> --- a/samples/rust/rust_misc_device.rs
> +++ b/samples/rust/rust_misc_device.rs
> @@ -136,7 +136,7 @@ fn init(_module: &'static ThisModule) -> impl PinInit<Self, Error> {
> };
>
> try_pin_init!(Self {
> - _miscdev <- MiscDeviceRegistration::register(options),
> + _miscdev <- MiscDeviceRegistration::register(options, ()),
> })
> }
> }
> @@ -156,6 +156,8 @@ struct RustMiscDevice {
> impl MiscDevice for RustMiscDevice {
> type Ptr = Pin<KBox<Self>>;
>
> + type RegistrationData = ();
> +
> fn open(_file: &File, misc: &MiscDeviceRegistration<Self>) -> Result<Pin<KBox<Self>>> {
> let dev = ARef::from(misc.device());
>
>
next prev parent reply other threads:[~2025-01-23 23:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 22:11 [PATCH 0/3] rust: miscdevice: Add additional data to MiscDeviceRegistration Christian Schrefl
2025-01-19 22:11 ` [PATCH 1/3] rust: add Aliased type Christian Schrefl
2025-01-19 23:04 ` Miguel Ojeda
2025-01-20 0:27 ` Christian Schrefl
2025-01-20 17:24 ` Boqun Feng
2025-01-23 10:21 ` Christian Schrefl
2025-01-23 17:56 ` Boqun Feng
2025-01-23 18:04 ` Christian Schrefl
2025-01-23 18:25 ` Boqun Feng
2025-01-23 20:18 ` Christian Schrefl
2025-01-23 20:24 ` Boqun Feng
2025-01-23 20:27 ` Christian Schrefl
2025-01-19 22:11 ` [PATCH 2/3] rust: miscdevice: Add additional data to MiscDeviceRegistration Christian Schrefl
2025-01-20 0:27 ` Christian Schrefl
2025-01-21 10:53 ` kernel test robot
2025-01-22 9:28 ` Greg Kroah-Hartman
2025-01-22 10:11 ` Alice Ryhl
2025-01-22 12:40 ` Greg Kroah-Hartman
2025-01-22 13:06 ` Alice Ryhl
2025-01-23 10:02 ` Christian Schrefl
2025-01-23 15:52 ` Christian Schrefl
2025-01-23 16:00 ` Greg Kroah-Hartman
2025-01-23 16:04 ` Christian Schrefl
2025-01-23 23:26 ` Christian Schrefl [this message]
2025-01-27 10:27 ` Alice Ryhl
2025-01-27 13:27 ` Christian Schrefl
2025-01-27 13:33 ` Alice Ryhl
2025-01-27 13:35 ` Christian Schrefl
2025-01-27 13:42 ` Miguel Ojeda
2025-01-19 22:11 ` [PATCH 3/3] rust: miscdevice: adjust the rust_misc_device sample to use RegistrationData Christian Schrefl
2025-01-21 15:40 ` Alice Ryhl
2025-01-23 17:57 ` Christian Schrefl
2025-01-24 7:29 ` Alice Ryhl
2025-01-24 8:06 ` Greg Kroah-Hartman
2025-01-24 9:42 ` Alice Ryhl
2025-01-24 10:34 ` Greg Kroah-Hartman
2025-01-24 10:39 ` Alice Ryhl
2025-01-24 11:22 ` Greg Kroah-Hartman
2025-01-24 11:37 ` Alice Ryhl
2025-01-24 11:42 ` Christian Schrefl
2025-01-20 5:46 ` [PATCH 0/3] rust: miscdevice: Add additional data to MiscDeviceRegistration Greg Kroah-Hartman
2025-01-21 10:29 ` Christian Schrefl
2025-01-22 9:22 ` Greg Kroah-Hartman
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=8953765e-d978-4a91-bc81-9ab154ac2255@gmail.com \
--to=chrisi.schrefl@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@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