mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Deborah Brouwer <deborah.brouwer@collabora.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Tamir Duberstein" <tamird@kernel.org>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Onur Özkan" <work@onurozkan.dev>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 2/2] drm/tyr: allow userspace buffers to be mismatched
Date: Mon, 19 Oct 2026 16:46:07 -0700	[thread overview]
Message-ID: <atarvxFKYYuHhXGQ@um790> (raw)
In-Reply-To: <atXOd-EeFkdA-trn@google.com>

On Mon, Oct 19, 2026 at 08:01:59AM +0000, Alice Ryhl wrote:
> On Fri, Oct 16, 2026 at 01:44:21PM -0700, Deborah Brouwer wrote:
> > Allow userspace to provide a buffer that is smaller or larger than the
> > object that the kernel expects to write into it.
> > 
> > Set a minimum buffer size to match those in PANTHOR_UOBJ_MIN_SIZE. If
> > userspace provides at least the minimum buffer size, then simply write
> > until the buffer is full.
> > 
> > If userspace provides a larger buffer than necessary, then zero out the
> > remaining buffer.
> > 
> > This ensures UAPI compatibility with Panthor.
> > 
> > Signed-off-by: Deborah Brouwer <deborah.brouwer@collabora.com>
> > ---
> >  drivers/gpu/drm/tyr/file.rs | 47 +++++++++++++++++++++++++++++++++++++--------
> >  1 file changed, 39 insertions(+), 8 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/tyr/file.rs b/drivers/gpu/drm/tyr/file.rs
> > index 9f60a90d4948..a153aa453ed1 100644
> > --- a/drivers/gpu/drm/tyr/file.rs
> > +++ b/drivers/gpu/drm/tyr/file.rs
> > @@ -1,11 +1,18 @@
> >  // SPDX-License-Identifier: GPL-2.0 or MIT
> >  
> > +use core::mem::{
> > +    offset_of,
> > +    size_of_val, //
> > +};
> 
> size_of_val is present in kernel::prelude::* and does not need explicit
> import.

Ack, will fix in next version.

> 
> > +    transmute::AsBytes,
> 
> Usie the trait from zerocopy instead.

If this other series making zerocopy available to Tyr gets merged,
then I could rebase this series on it and switch over to IntoBytes:

https://lore.kernel.org/rust-for-linux/20261019-b4-gpu_info_intobytes-v4-0-0bc04df46549@collabora.com/T/#m9a9a24e0cf1ae10451e3fc84955873b405d0da0b

> 
> > +    let mut writer = UserSlice::new(UserPtr::from_addr(usr_dst as usize), size).writer();
> 
> On 32-bit this will truncate upper bits. I guess that probably matches
> what Panthor does. Is it what we want?

Yes, that's what Panthor does; it uses the "u64_to_user_ptr()" macro to do
this deliberately.

Since UserPtr only accepts a usize argument, I have to cast in Tyr,
but instead, what do you think if I added another method to UserPtr
to accept a u64 address and cast it to usize just like in the C macro.
Something like:

    /// Create a `UserPtr` from a u64 userspace address.
    ///
    /// Deliberately truncate upper bits for 32-bit systems.
    #[doc(alias = "u64_to_user_ptr")]
    #[inline]
    pub fn from_u64(addr: u64) -> Self {
        Self::from_addr(addr as usize)
    }

> 
> Alice

      reply	other threads:[~2026-10-19 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 20:44 [PATCH v3 0/2] drm/tyr: allow mismatched buffers for dev_query Deborah Brouwer
2026-10-16 20:44 ` [PATCH v3 1/2] rust: uaccess: add UserSliceWriter::clear() Deborah Brouwer
2026-10-16 20:44 ` [PATCH v3 2/2] drm/tyr: allow userspace buffers to be mismatched Deborah Brouwer
2026-10-19  8:01   ` Alice Ryhl
2026-10-19 23:46     ` Deborah Brouwer [this message]

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=atarvxFKYYuHhXGQ@um790 \
    --to=deborah.brouwer@collabora.com \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=work@onurozkan.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 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®