From: Markus Probst <markus.probst@posteo.de>
To: Alice Ryhl <aliceryhl@google.com>
Cc: Danilo Krummrich <dakr@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>, Lee Jones <lee@kernel.org>,
Pavel Machek <pavel@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Uladzislau Rezki <urezki@gmail.com>,
Boqun Feng <boqun.feng@gmail.com>, Gary Guo <gary@garyguo.net>,
bjorn3_gh@protonmail.com, Benno Lossin <lossin@kernel.org>,
Andreas Hindborg <a.hindborg@kernel.org>,
Trevor Gross <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v2 1/2] rust: add basic Pin<Vec<T, A>> abstractions
Date: Fri, 10 Oct 2025 21:14:07 +0000 [thread overview]
Message-ID: <b3a2617eda71a4a4ca0e0181afc26a33d42b1ba9.camel@posteo.de> (raw)
In-Reply-To: <aOjvAozHB8T2PZbm@google.com>
I might be wrong here, but as far as I know, it is not possible to get
a `Pin<&mut Vec<T, A>>` from a `&mut Pin<Vec<T, A>>`, only a `&mut
Pin<&mut [T, A]>` which is not usable by any of these methods.
Thanks
- Markus Probst
On Fri, 2025-10-10 at 11:33 +0000, Alice Ryhl wrote:
> On Thu, Oct 09, 2025 at 06:12:33PM +0000, Markus Probst wrote:
> > Implement core Pin<Vec<T, A>> abstractions, including
> > * `Vec::pin` and `Vec::into_pin` for constructing a `Pin<Vec<T,
> > A>>`.
> > If T does not implement `Unpin`, its values will never be moved.
> > * an extension for `Pin<Vec<T, A>>` allowing PinInit to be
> > initialied on a
> > Pin<Vec>, as well as truncating and popping values from the Vec
> >
> > Signed-off-by: Markus Probst <markus.probst@posteo.de>
> > ---
> > rust/kernel/alloc.rs | 1 +
> > rust/kernel/alloc/kvec.rs | 86
> > +++++++++++++++++++++++++++++++++++++++
> > rust/kernel/prelude.rs | 2 +-
> > 3 files changed, 88 insertions(+), 1 deletion(-)
> >
> > diff --git a/rust/kernel/alloc.rs b/rust/kernel/alloc.rs
> > index a2c49e5494d3..9c129eaf0625 100644
> > --- a/rust/kernel/alloc.rs
> > +++ b/rust/kernel/alloc.rs
> > @@ -24,6 +24,7 @@
> > pub use self::kvec::KVec;
> > pub use self::kvec::VVec;
> > pub use self::kvec::Vec;
> > +pub use self::kvec::PinnedVecExt;
> >
> > /// Indicates an allocation error.
> > #[derive(Copy, Clone, PartialEq, Eq, Debug)]
> > diff --git a/rust/kernel/alloc/kvec.rs b/rust/kernel/alloc/kvec.rs
> > index 3c72e0bdddb8..d5582a7f17e9 100644
> > --- a/rust/kernel/alloc/kvec.rs
> > +++ b/rust/kernel/alloc/kvec.rs
> > @@ -16,11 +16,13 @@
> > ops::DerefMut,
> > ops::Index,
> > ops::IndexMut,
> > + pin::Pin,
> > ptr,
> > ptr::NonNull,
> > slice,
> > slice::SliceIndex,
> > };
> > +use pin_init::PinInit;
> >
> > mod errors;
> > pub use self::errors::{InsertError, PushError, RemoveError};
> > @@ -109,6 +111,21 @@ pub struct Vec<T, A: Allocator> {
> > _p: PhantomData<A>,
> > }
> >
> > +/// Extension for Pin<Vec<T, A>>
> > +pub trait PinnedVecExt<T> {
> > + /// Pin-initializes P and appends it to the back of the
> > [`Vec`] instance without reallocating.
> > + fn push_pin_init<E: From<PushError<P>>, P: PinInit<T, E>>(&mut
> > self, init: P) -> Result<(), E>;
> > +
> > + /// Shortens the vector, setting the length to `len` and drops
> > the removed values.
> > + /// If `len` is greater than or equal to the current length,
> > this does nothing.
> > + ///
> > + /// This has no effect on the capacity and will not allocate.
> > + fn truncate(&mut self, len: usize);
> > +
> > + /// Removes the last element from a vector and drops it
> > returning true, or false if it is empty.
> > + fn pop(&mut self) -> bool;
> > +}
>
> Please no extension traits just for this. Just provide `self:
> Pin<&mut Self>`
> methods on Vec.
>
> Alice
next prev parent reply other threads:[~2025-10-10 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 18:12 [PATCH v2 0/2] rust: leds: add led classdev abstractions Markus Probst
2025-10-09 18:12 ` [PATCH v2 1/2] rust: add basic Pin<Vec<T, A>> abstractions Markus Probst
2025-10-10 11:33 ` Alice Ryhl
2025-10-10 21:14 ` Markus Probst [this message]
2025-10-09 18:12 ` [PATCH v2 2/2] rust: leds: add basic led classdev abstractions Markus Probst
2025-10-10 11:41 ` Alice Ryhl
2025-10-10 13:03 ` Markus Probst
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=b3a2617eda71a4a4ca0e0181afc26a33d42b1ba9.camel@posteo.de \
--to=markus.probst@posteo.de \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=pavel@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
/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
all inboxes | Powered by JetHome®