From: "Benno Lossin" <lossin@kernel.org>
To: "Danilo Krummrich" <dakr@kernel.org>,
	<gregkh@linuxfoundation.org>, <rafael@kernel.org>
Cc: <viresh.kumar@linaro.org>, <acourbot@nvidia.com>,
	<ira.weiny@intel.com>, <leon@kernel.org>,
	<daniel.almeida@collabora.com>, <bhelgaas@google.com>,
	<kwilczynski@kernel.org>, <abdiel.janulgue@gmail.com>,
	<robin.murphy@arm.com>, <ojeda@kernel.org>,
	<alex.gaynor@gmail.com>, <boqun.feng@gmail.com>,
	<gary@garyguo.net>, <bjorn3_gh@protonmail.com>,
	<a.hindborg@kernel.org>, <aliceryhl@google.com>,
	<tmgross@umich.edu>, <rust-for-linux@vger.kernel.org>,
	<linux-pci@vger.kernel.org>, <linux-pm@vger.kernel.org>,
	<nouveau@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rust: driver: let probe() return impl PinInit<Self, Error>
Date: Thu, 16 Oct 2025 23:48:25 +0200	[thread overview]
Message-ID: <DDK2SRUF7OG7.1HEZXR1V4ND8Z@kernel.org> (raw)
In-Reply-To: <20251016125544.15559-1-dakr@kernel.org>
On Thu Oct 16, 2025 at 2:55 PM CEST, Danilo Krummrich wrote:
> The driver model defines the lifetime of the private data stored in (and
> owned by) a bus device to be valid from when the driver is bound to a
> device (i.e. from successful probe()) until the driver is unbound from
> the device.
>
> This is already taken care of by the Rust implementation of the driver
> model. However, we still ask drivers to return a Result<Pin<KBox<Self>>>
> from probe().
>
> Unlike in C, where we do not have the concept of initializers, but
> rather deal with uninitialized memory, drivers can just return an
> impl PinInit<Self, Error> instead.
>
> This contributed to more clarity to the fact that a driver returns it's
> device private data in probe() and the Rust driver model owns the data,
> manages the lifetime and - considering the lifetime - provides (safe)
> accessors for the driver.
>
> Hence, let probe() functions return an impl PinInit<Self, Error> instead
> of Result<Pin<KBox<Self>>>.
>
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> ---
> Depends on a minor pin-init patch [1] (Benno will send it to the list
> soon). A branch with this patch and the pin-init dependency is available
> in [2].
I sent the patch to the list:
    https://lore.kernel.org/all/20251016210541.650056-1-lossin@kernel.org
---
Cheers,
Benno
>
> [1] https://github.com/Rust-for-Linux/pin-init/pull/86/commits
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/dakr/linux.git/log/?h=probe_return
> ---
>  drivers/cpufreq/rcpufreq_dt.rs        |  4 +-
>  drivers/gpu/drm/nova/driver.rs        |  4 +-
>  drivers/gpu/drm/tyr/driver.rs         |  4 +-
>  drivers/gpu/nova-core/driver.rs       | 34 +++++++----------
>  rust/kernel/auxiliary.rs              |  6 +--
>  rust/kernel/cpufreq.rs                |  4 +-
>  rust/kernel/device.rs                 |  9 ++++-
>  rust/kernel/driver.rs                 |  4 +-
>  rust/kernel/io/mem.rs                 |  8 ++--
>  rust/kernel/pci.rs                    |  8 ++--
>  rust/kernel/platform.rs               | 12 +++---
>  rust/kernel/usb.rs                    |  4 +-
>  samples/rust/rust_debugfs.rs          | 21 ++++++-----
>  samples/rust/rust_dma.rs              | 37 +++++++++----------
>  samples/rust/rust_driver_auxiliary.rs | 25 +++++--------
>  samples/rust/rust_driver_pci.rs       | 53 +++++++++++++--------------
>  samples/rust/rust_driver_platform.rs  |  6 +--
>  samples/rust/rust_driver_usb.rs       |  5 +--
>  18 files changed, 117 insertions(+), 131 deletions(-)
next prev parent reply	other threads:[~2025-10-16 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 12:55 [PATCH] rust: driver: let probe() return impl PinInit<Self, Error> Danilo Krummrich
2025-10-16 21:48 ` Benno Lossin [this message]
2025-10-17  2:12 ` Alexandre Courbot
2025-10-17  8:26   ` Benno Lossin
2025-10-17  4:04 ` Viresh Kumar
2025-10-17 13:04 ` Alice Ryhl
2025-10-17 18:29   ` Danilo Krummrich
2025-10-21  7:05 ` Greg KH
2025-10-21 17:43 ` Danilo Krummrich
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=DDK2SRUF7OG7.1HEZXR1V4ND8Z@kernel.org \
    --to=lossin@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=abdiel.janulgue@gmail.com \
    --cc=acourbot@nvidia.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=ira.weiny@intel.com \
    --cc=kwilczynski@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=ojeda@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=viresh.kumar@linaro.org \
    /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).