All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Price <steven.price@arm.com>
To: Emil Velikov <emil.l.velikov@gmail.com>, dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
	Robin Murphy <robin.murphy@arm.com>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>
Subject: Re: [PATCH 4/5] drm/panfrost: remove DRM_AUTH and respective comment
Date: Fri, 1 Nov 2019 13:34:36 +0000	[thread overview]
Message-ID: <d652ceaa-2c64-31f0-1793-14a5de51dc57@arm.com> (raw)
In-Reply-To: <20191101130313.8862-4-emil.l.velikov@gmail.com>

On 01/11/2019 13:03, Emil Velikov wrote:
> From: Emil Velikov <emil.velikov@collabora.com>
> 
> As of earlier commit we have address space separation. Yet we forgot to
> remove the respective comment and DRM_AUTH in the ioctl declaration.
> 
> Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> Cc: David Airlie <airlied@linux.ie>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Steven Price <steven.price@arm.com>
> Fixes: 7282f7645d06 ("drm/panfrost: Implement per FD address spaces")
> Signed-off-by: Emil Velikov <emil.velikov@collabora.com>

Reviewed-by: Steven Price <steven.price@arm.com>

I'm not sure DRM_AUTH provided us with much in the first place (because
render nodes could snoop/affect the primary node), but since we have
address space separation it's clearly not required now.

Steve

> ---
>  drivers/gpu/drm/panfrost/panfrost_drv.c | 6 +-----
>  1 file changed, 1 insertion(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/panfrost/panfrost_drv.c b/drivers/gpu/drm/panfrost/panfrost_drv.c
> index bc2ddeb55f5d..c677b2c9e409 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_drv.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_drv.c
> @@ -451,15 +451,11 @@ panfrost_postclose(struct drm_device *dev, struct drm_file *file)
>  	kfree(panfrost_priv);
>  }
>  
> -/* DRM_AUTH is required on SUBMIT for now, while all clients share a single
> - * address space.  Note that render nodes would be able to submit jobs that
> - * could access BOs from clients authenticated with the master node.
> - */
>  static const struct drm_ioctl_desc panfrost_drm_driver_ioctls[] = {
>  #define PANFROST_IOCTL(n, func, flags) \
>  	DRM_IOCTL_DEF_DRV(PANFROST_##n, panfrost_ioctl_##func, flags)
>  
> -	PANFROST_IOCTL(SUBMIT,		submit,		DRM_RENDER_ALLOW | DRM_AUTH),
> +	PANFROST_IOCTL(SUBMIT,		submit,		DRM_RENDER_ALLOW),
>  	PANFROST_IOCTL(WAIT_BO,		wait_bo,	DRM_RENDER_ALLOW),
>  	PANFROST_IOCTL(CREATE_BO,	create_bo,	DRM_RENDER_ALLOW),
>  	PANFROST_IOCTL(MMAP_BO,		mmap_bo,	DRM_RENDER_ALLOW),
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-11-01 13:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01 13:03 [PATCH 1/5] drm/vmwgfx: move the require_exist handling together Emil Velikov
2019-11-01 13:03 ` [PATCH 2/5] drm/vmwgfx: check master authentication in surface_ref ioctls Emil Velikov
2019-11-12 12:53   ` Thomas Hellstrom
2019-11-01 13:03 ` [PATCH 3/5] drm/vmwgfx: drop DRM_AUTH for render ioctls Emil Velikov
2019-11-12 12:54   ` Thomas Hellstrom
2019-11-13 14:48     ` Emil Velikov
2019-11-01 13:03 ` [PATCH 4/5] drm/panfrost: remove DRM_AUTH and respective comment Emil Velikov
2019-11-01 13:34   ` Steven Price [this message]
2019-11-08 13:10     ` Emil Velikov
2019-11-08 15:55       ` Steven Price
2019-11-08 16:42         ` Emil Velikov
2019-11-01 13:03 ` [PATCH 5/5] drm: drop DRM_AUTH from PRIME_TO/FROM_HANDLE ioctls Emil Velikov
2019-11-01 13:03   ` Emil Velikov
     [not found]   ` <20191101130313.8862-5-emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-11-08 13:11     ` Emil Velikov
2019-11-08 13:11       ` Emil Velikov
2019-11-08 13:11       ` Emil Velikov
2019-11-27  7:41   ` Boris Brezillon
2019-11-27  7:41     ` Boris Brezillon
2019-11-27 16:27     ` Emil Velikov
2019-11-27 16:27       ` Emil Velikov
     [not found]       ` <CACvgo52UB-sAv55_kREgHbRsg6b5KXv7At0TbgUPdc0e1E+QaA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-11-27 18:04         ` Daniel Vetter
2019-11-27 18:04           ` Daniel Vetter
2019-11-27 18:04           ` Daniel Vetter
     [not found]           ` <20191127180456.GD406127-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-11-27 18:32             ` Emil Velikov
2019-11-27 18:32               ` Emil Velikov
2019-11-27 18:32               ` Emil Velikov
     [not found]               ` <CACvgo50j0sU18-AqeerkgDq9joJysT_0PuQrgVS1tVhUqV9rcg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-11-27 18:37                 ` Daniel Vetter
2019-11-27 18:37                   ` Daniel Vetter
2019-11-27 18:37                   ` Daniel Vetter
     [not found]                   ` <20191127183700.GN406127-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-12-02 17:20                     ` Emil Velikov
2019-12-02 17:20                       ` Emil Velikov
2019-12-02 17:20                       ` Emil Velikov
2019-11-27 16:25   ` [PATCH v2] " Emil Velikov
2019-11-27 16:25     ` Emil Velikov
2019-11-08 13:13 ` [PATCH 1/5] drm/vmwgfx: move the require_exist handling together Emil Velikov
2019-11-08 15:22   ` Thomas Hellstrom
2019-11-12 12:50 ` Thomas Hellstrom

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=d652ceaa-2c64-31f0-1793-14a5de51dc57@arm.com \
    --to=steven.price@arm.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=tomeu.vizoso@collabora.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 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.