From: sashiko-bot@kernel.org
To: "Philipp Stanner" <phasta@kernel.org>
Cc: dri-devel@lists.freedesktop.org, ojeda@kernel.org, media-ci@linuxtv.org
Subject: Re: [PATCH v9 2/5] rust: types: implement ForeignOwnable for ARef<T>
Date: Wed, 05 Aug 2026 15:22:34 +0000 [thread overview]
Message-ID: <20260805152235.4AFE91F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260805145949.938505-4-phasta@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing `#[inline]` annotations on small forwarding methods within an abstraction.
--
--- Patch [2]: [PATCH v9 2/5] rust: types: implement ForeignOwnable for ARef<T> ---
commit 46a32182bbc01f0e36763ebdf80c949f544fec26
Author: Danilo Krummrich <dakr@kernel.org>
rust: types: implement ForeignOwnable for ARef<T>
Implement ForeignOwnable for ARef<T>, making it possible for C code to
own an ARef<T>. Since ARef represents shared ownership, BorrowedMut is
&T rather than &mut T, matching the semantics of the underlying type.
> diff --git a/rust/kernel/sync/aref.rs b/rust/kernel/sync/aref.rs
> index b721b2e00b986..5407666136595 100644
> --- a/rust/kernel/sync/aref.rs
> +++ b/rust/kernel/sync/aref.rs
[ ... ]
> @@ -188,6 +193,41 @@ fn eq(&self, other: &ARef<U>) -> bool {
> }
> impl<T: AlwaysRefCounted + Eq> Eq for ARef<T> {}
>
> +// SAFETY: `into_foreign` returns a pointer from `NonNull::as_ptr`, so it's non-null. The
> +// `ARef` invariant guarantees that `ptr` points to a valid `T`, so it's aligned to `T`.
> +unsafe impl<T: AlwaysRefCounted + 'static> ForeignOwnable for ARef<T> {
> + const FOREIGN_ALIGN: usize = core::mem::align_of::<T>();
> +
> + type Borrowed<'a> = &'a T;
> + type BorrowedMut<'a> = &'a T;
> +
> + fn into_foreign(self) -> *mut c_void {
> + ARef::into_raw(self).as_ptr().cast()
> + }
[Severity: Low]
This isn't a bug, but according to the Rust subsystem guidelines, small or
forwarding functions within abstractions should be annotated with #[inline].
Would it be appropriate to add the #[inline] attribute to into_foreign() here?
> +
> + unsafe fn from_foreign(ptr: *mut c_void) -> Self {
> + // SAFETY: The safety requirements of this function ensure that `ptr` comes from a previous
> + // call to `Self::into_foreign`.
> + let ptr = unsafe { NonNull::new_unchecked(ptr.cast()) };
> +
> + // SAFETY: `ptr` came from `into_foreign`, which consumed an `ARef` without decrementing
> + // the refcount, so we can transfer the ownership to the new `ARef`.
> + unsafe { ARef::from_raw(ptr) }
> + }
[Severity: Low]
Could from_foreign() also benefit from an #[inline] annotation, given it is
a small forwarding function?
> +
> + unsafe fn borrow<'a>(ptr: *mut c_void) -> &'a T {
> + // SAFETY: The safety requirements of this method ensure that the object remains alive and
> + // immutable for the duration of 'a.
> + unsafe { &*ptr.cast() }
> + }
[Severity: Low]
Similarly, should borrow() be annotated with #[inline] to match the subsystem
guidelines?
> +
> + unsafe fn borrow_mut<'a>(ptr: *mut c_void) -> &'a T {
> + // SAFETY: The safety requirements for `borrow_mut` are a superset of the safety
> + // requirements for `borrow`.
> + unsafe { <Self as ForeignOwnable>::borrow(ptr) }
> + }
[Severity: Low]
This function also appears to be a short forwarding wrapper. Is it missing the
#[inline] attribute as well?
> +}
> +
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260805145949.938505-2-phasta@kernel.org?part=2
next prev parent reply other threads:[~2026-08-05 15:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 14:59 [PATCH v9 0/5] rust / dma_buf: Add abstractions for dma_fence Philipp Stanner
2026-08-05 14:59 ` [PATCH v9 1/5] rust: error: add remaining error codes Philipp Stanner
2026-08-05 14:59 ` [PATCH v9 2/5] rust: types: implement ForeignOwnable for ARef<T> Philipp Stanner
2026-08-05 15:22 ` sashiko-bot [this message]
2026-08-05 18:23 ` Gary Guo
2026-08-06 14:31 ` Gary Guo
2026-08-05 14:59 ` [PATCH v9 3/5] rust: sync: Add abstraction for rcu_barrier() Philipp Stanner
2026-08-05 19:08 ` Gary Guo
2026-08-05 14:59 ` [PATCH v9 4/5] rust: Add dma_fence abstractions Philipp Stanner
2026-08-05 15:35 ` Daniel Almeida
2026-08-05 15:46 ` sashiko-bot
2026-08-06 13:56 ` Gary Guo
2026-08-11 9:46 ` Philipp Stanner
2026-08-05 14:59 ` [PATCH v9 5/5] MAINTAINERS: Add entry for Rust dma-buf Philipp Stanner
2026-08-05 16:11 ` [PATCH v9 0/5] rust / dma_buf: Add abstractions for dma_fence Danilo Krummrich
2026-08-10 6:00 ` Miguel Ojeda
2026-08-10 7:47 ` Philipp Stanner
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=20260805152235.4AFE91F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=media-ci@linuxtv.org \
--cc=ojeda@kernel.org \
--cc=phasta@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.