From: Alice Ryhl <aliceryhl@google.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Arnd Bergmann" <arnd@arndb.de>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Matthew Maurer" <mmaurer@google.com>,
"Lee Jones" <lee@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Benno Lossin" <lossin@kernel.org>,
"Christian Brauner" <brauner@kernel.org>
Subject: Re: [PATCH v4 3/4] rust: miscdevice: Provide additional abstractions for iov_iter and kiocb structures
Date: Wed, 13 Aug 2025 12:16:58 +0000 [thread overview]
Message-ID: <aJyCOstIjMuvzLwH@google.com> (raw)
In-Reply-To: <DC19RGJ4EPSK.1QRTOMYUKY34@kernel.org>
On Wed, Aug 13, 2025 at 01:39:12PM +0200, Danilo Krummrich wrote:
> On Wed Aug 13, 2025 at 10:27 AM CEST, Alice Ryhl wrote:
> > +pub struct Kiocb<'a, T> {
> > + inner: NonNull<bindings::kiocb>,
> > + _phantom: PhantomData<&'a T>,
> > +}
> > +
> > +impl<'a, T: ForeignOwnable> Kiocb<'a, T> {
> > + /// Create a `Kiocb` from a raw pointer.
> > + ///
> > + /// # Safety
> > + ///
> > + /// The pointer must reference a valid `struct kiocb` for the duration of `'a`. The private
> > + /// data of the file must be `T`.
> > + pub unsafe fn from_raw(kiocb: *mut bindings::kiocb) -> Self {
> > + Self {
> > + // SAFETY: If a pointer is valid it is not null.
> > + inner: unsafe { NonNull::new_unchecked(kiocb) },
> > + _phantom: PhantomData,
> > + }
> > + }
> > +
> > + /// Access the underlying `struct kiocb` directly.
> > + pub fn as_raw(&self) -> *mut bindings::kiocb {
> > + self.inner.as_ptr()
> > + }
> > +
> > + /// Get the filesystem or driver specific data associated with the file.
> > + pub fn file(&self) -> <T as ForeignOwnable>::Borrowed<'a> {
> > + // SAFETY: We have shared access to this kiocb and hence the underlying file, so we can
> > + // read the file's private data.
> > + let private = unsafe { (*(*self.as_raw()).ki_filp).private_data };
> > + // SAFETY: The kiocb has shared access to the private data.
> > + unsafe { <T as ForeignOwnable>::borrow(private) }
> > + }
> > +
> > + /// Gets the current value of `ki_pos`.
> > + pub fn ki_pos(&self) -> i64 {
> > + // SAFETY: We have shared access to the kiocb, so we can read its `ki_pos` field.
> > + unsafe { (*self.as_raw()).ki_pos }
> > + }
> > +
> > + /// Gets a mutable reference to the `ki_pos` field.
> > + pub fn ki_pos_mut(&mut self) -> &mut i64 {
> > + // SAFETY: We have exclusive access to the kiocb, so we can write to `ki_pos`.
> > + unsafe { &mut (*self.as_raw()).ki_pos }
> > + }
> > +}
>
> I think this should be a separate commit.
I can split it.
Alice
next prev parent reply other threads:[~2025-08-13 12:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 8:27 [PATCH v4 0/4] Rust support for `struct iov_iter` Alice Ryhl
2025-08-13 8:27 ` [PATCH v4 1/4] rust: iov: add iov_iter abstractions for ITER_SOURCE Alice Ryhl
2025-08-13 11:27 ` Danilo Krummrich
2025-08-13 11:40 ` Miguel Ojeda
2025-08-13 12:16 ` Alice Ryhl
2025-08-13 8:27 ` [PATCH v4 2/4] rust: iov: add iov_iter abstractions for ITER_DEST Alice Ryhl
2025-08-13 11:34 ` Danilo Krummrich
2025-08-13 13:33 ` Benoît du Garreau
2025-08-14 7:57 ` Alice Ryhl
2025-08-13 8:27 ` [PATCH v4 3/4] rust: miscdevice: Provide additional abstractions for iov_iter and kiocb structures Alice Ryhl
2025-08-13 11:39 ` Danilo Krummrich
2025-08-13 12:16 ` Alice Ryhl [this message]
2025-08-15 9:56 ` Andreas Hindborg
2025-08-13 8:27 ` [PATCH v4 4/4] samples: rust_misc_device: Expand the sample to support read()ing from userspace Alice Ryhl
2025-08-13 11:20 ` [PATCH v4 0/4] Rust support for `struct iov_iter` Danilo Krummrich
2025-08-19 9:03 ` 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=aJyCOstIjMuvzLwH@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=arnd@arndb.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mmaurer@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=viro@zeniv.linux.org.uk \
/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).