dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: Kristian Hoegsberg <hoegsberg@gmail.com>
Subject: Re: [PATCH] drm: fix returning -EINVAL on setmaster if another master is active
Date: Thu, 11 Oct 2012 12:35:03 +0200	[thread overview]
Message-ID: <1477778.PIc27Jio4Y@avalon> (raw)
In-Reply-To: <1349632406-24068-1-git-send-email-dh.herrmann@googlemail.com>

Hi David,

Would you have time to document the master_set operation in 
Documentation/DocBook/drm.tmpl ? :-)

On Sunday 07 October 2012 19:53:26 David Herrmann wrote:
> We link every DRM "file_priv" to a "drm_master" structure. Currently, the
> drmSetMaster() call returns 0 when there is _any_ active master associated
> with the "drm_master" structure of the calling "file_priv". This means,
> that after drmSetMaster() we are not guaranteed to be DRM-Master and might
> not be able to perform mode-setting.
> 
> A way to reproduce this is by starting weston with the DRM backend from
> within an X-console (eg., xterm). Because the xserver's "drm_master" is
> currently active, weston is assigned to the same master but is inactive
> because its VT is inactive and the xserver is still active. But when
> "fake-activating" weston, it calls drmSetMaster(). With current behavior
> this returns "0/success" and weston thinks that it is DRM-Master, even
> though it is not (as the xserver is still DRM-Master).
> Expected behavior would be drmSetMaster() to return -EINVAL, because the
> xserver is still DRM-Master. This patch changes exactly that.
> 
> The only way this bogus behavior would be useful is for clients to check
> whether their associated "drm_master" is currently the active DRM-Master.
> But this logic fails if no DRM-Master is currently active at all. Because
> then the client itself would become DRM-Master (if it is root) and this
> makes this whole thing useles.
> 
> Also note that the second "if-condition":
>   file_priv->minor->master != file_priv->master
> is always true and can be skipped.
> 
> Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
> ---
> Note:
> Note that this only removes the "if-clause". The code that performs the
> setmaster() is actually left unchanged but makes the patch look scarier than
> it really is.
> 
>  drivers/gpu/drm/drm_stub.c | 24 ++++++++++++------------
>  1 file changed, 12 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_stub.c b/drivers/gpu/drm/drm_stub.c
> index c236fd2..581e61d 100644
> --- a/drivers/gpu/drm/drm_stub.c
> +++ b/drivers/gpu/drm/drm_stub.c
> @@ -221,20 +221,20 @@ int drm_setmaster_ioctl(struct drm_device *dev, void
> *data, if (!file_priv->master)
>  		return -EINVAL;
> 
> -	if (!file_priv->minor->master &&
> -	    file_priv->minor->master != file_priv->master) {
> -		mutex_lock(&dev->struct_mutex);
> -		file_priv->minor->master = drm_master_get(file_priv->master);
> -		file_priv->is_master = 1;
> -		if (dev->driver->master_set) {
> -			ret = dev->driver->master_set(dev, file_priv, false);
> -			if (unlikely(ret != 0)) {
> -				file_priv->is_master = 0;
> -				drm_master_put(&file_priv->minor->master);
> -			}
> +	if (file_priv->minor->master)
> +		return -EINVAL;
> +
> +	mutex_lock(&dev->struct_mutex);
> +	file_priv->minor->master = drm_master_get(file_priv->master);
> +	file_priv->is_master = 1;
> +	if (dev->driver->master_set) {
> +		ret = dev->driver->master_set(dev, file_priv, false);
> +		if (unlikely(ret != 0)) {
> +			file_priv->is_master = 0;
> +			drm_master_put(&file_priv->minor->master);
>  		}
> -		mutex_unlock(&dev->struct_mutex);
>  	}
> +	mutex_unlock(&dev->struct_mutex);
> 
>  	return 0;
>  }

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2012-10-11 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 17:53 [PATCH] drm: fix returning -EINVAL on setmaster if another master is active David Herrmann
2012-10-11 10:35 ` Laurent Pinchart [this message]
2012-10-11 10:41   ` David Herrmann
2012-10-11 11:12     ` Laurent Pinchart

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=1477778.PIc27Jio4Y@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hoegsberg@gmail.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).