All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH -next] drm/vmwgfx: Allow dropped masters render-node like access on legacy nodes
Date: Thu, 27 Aug 2015 15:07:24 +0200	[thread overview]
Message-ID: <55DF0B8C.2010408@vmware.com> (raw)
In-Reply-To: <1440680124-3568-1-git-send-email-thellstrom@vmware.com>

On 08/27/2015 02:55 PM, Thomas Hellstrom wrote:
> Applications like gnome-shell may try to render after dropping master
> privileges. Since the driver should now be safe against this scenario,
> allow those applications to use their legacy node like a render node.
>
> Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
> Reviewed-by: Sinclair Yeh <syeh@vmware.com>
> ---
>  drivers/gpu/drm/vmwgfx/vmwgfx_drv.c     | 7 ++++++-
>  drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 5 +++++
>  2 files changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> index 03854d6..e13b20b 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> @@ -1052,10 +1052,15 @@ static struct vmw_master *vmw_master_check(struct drm_device *dev,
>  	}
>  
>  	/*
> -	 * Check if we were previously master, but now dropped.
> +	 * Check if we were previously master, but now dropped. In that
> +	 * case, allow at least render node functionality.
>  	 */
>  	if (vmw_fp->locked_master) {
>  		mutex_unlock(&dev->master_mutex);
> +
> +		if (flags & DRM_RENDER_ALLOW)
> +			return NULL;
> +
>  		DRM_ERROR("Dropped master trying to access ioctl that "
>  			  "requires authentication.\n");
>  		return ERR_PTR(-EACCES);
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_surface.c b/drivers/gpu/drm/vmwgfx/vmwgfx_surface.c
> index 5b8595b..4f0794d 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_surface.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_surface.c
> @@ -911,6 +911,11 @@ vmw_surface_handle_reference(struct vmw_private *dev_priv,
>  				  "surface reference.\n");
>  			return -EACCES;
>  		}
> +		if (ACCESS_ONCE(vmw_fpriv(file_priv)->locked_master)) {
> +			DRM_ERROR("Locked master refused legacy "
> +				  "surface reference.\n");

Actually, a return -EACCES is missing here. I'll send out a v2.

/Thomas

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

      reply	other threads:[~2015-08-27 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 12:55 [PATCH -next] drm/vmwgfx: Allow dropped masters render-node like access on legacy nodes Thomas Hellstrom
2015-08-27 13:07 ` Thomas Hellstrom [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=55DF0B8C.2010408@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=dri-devel@lists.freedesktop.org \
    /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.