From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Gurchetan Singh <gurchetansingh@chromium.org>,
dri-devel@lists.freedesktop.org
Cc: josh.simonot@gmail.com, kraxel@redhat.com
Subject: Re: [PATCH v3 2/2] drm/uapi: add explicit virtgpu context debug name
Date: Sun, 12 Nov 2023 01:37:11 +0300 [thread overview]
Message-ID: <9b2f45e1-ea49-97ae-e359-3f9c0996394f@collabora.com> (raw)
In-Reply-To: <20231018181727.772-2-gurchetansingh@chromium.org>
On 10/18/23 21:17, Gurchetan Singh wrote:
> + case VIRTGPU_CONTEXT_PARAM_DEBUG_NAME:
> + if (vfpriv->explicit_debug_name) {
> + ret = -EINVAL;
> + goto out_unlock;
> + }
> +
> + ret = strncpy_from_user(vfpriv->debug_name,
> + u64_to_user_ptr(value),
> + DEBUG_NAME_MAX_LEN - 1);
> +
> + if (ret < 0) {
> + ret = -EFAULT;
> + goto out_unlock;
> + }
> +
> + vfpriv->explicit_debug_name = true;
> + break;
Spotted a problem here. The ret needs to be set to zero on success. I'll
send the fix shortly. Gurchetan you should've been getting the
DRM_IOCTL_VIRTGPU_CONTEXT_INIT failure from gfxstream when you tested
this patch, haven't you?
Also noticed that the patch title says "drm/uapi" instead of
"drm/virtio". My bad for not noticing it earlier. Please be more careful
next time too :)
--
Best regards,
Dmitry
next prev parent reply other threads:[~2023-11-11 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 18:17 [PATCH v3 1/2] drm/virtio: use uint64_t more in virtio_gpu_context_init_ioctl Gurchetan Singh
2023-10-18 18:17 ` [PATCH v3 2/2] drm/uapi: add explicit virtgpu context debug name Gurchetan Singh
2023-10-18 22:59 ` Dmitry Osipenko
2023-10-22 23:50 ` Dmitry Osipenko
2023-10-31 15:55 ` Gurchetan Singh
2023-11-10 17:26 ` Gurchetan Singh
2023-11-11 18:40 ` Dmitry Osipenko
2023-11-11 22:37 ` Dmitry Osipenko [this message]
2023-11-13 17:04 ` Gurchetan Singh
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=9b2f45e1-ea49-97ae-e359-3f9c0996394f@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=josh.simonot@gmail.com \
--cc=kraxel@redhat.com \
/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).