dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/prime: cleanup prime/gem locking interaction
Date: Thu, 15 Oct 2015 08:41:09 +0200	[thread overview]
Message-ID: <20151015064109.GP26718@phenom.ffwll.local> (raw)
In-Reply-To: <1444873901-32043-5-git-send-email-airlied@gmail.com>

On Thu, Oct 15, 2015 at 11:51:41AM +1000, Dave Airlie wrote:
> From: Dave Airlie <airlied@redhat.com>
> 
> calling drm_gem_handle_delete would cause an attempt to retake
> the prime lock.
> 
> move code around so we never need to do that. This patch allocates
> the member structure early, so there is no failure path that
> requires calling drm_gem_handle_delete.
> 
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> ---
>  drivers/gpu/drm/drm_prime.c | 49 ++++++++++++++++++++++-----------------------
>  1 file changed, 24 insertions(+), 25 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c
> index 88c004e..6991398 100644
> --- a/drivers/gpu/drm/drm_prime.c
> +++ b/drivers/gpu/drm/drm_prime.c
> @@ -71,20 +71,14 @@ struct drm_prime_attachment {
>  	enum dma_data_direction dir;
>  };
>  
> -static int drm_prime_add_buf_handle(struct drm_prime_file_private *prime_fpriv,
> -				    struct dma_buf *dma_buf, uint32_t handle)
> +static void drm_prime_add_buf_handle(struct drm_prime_file_private *prime_fpriv,
> +				     struct drm_prime_member *member,
> +				     struct dma_buf *dma_buf, uint32_t handle)
>  {
> -	struct drm_prime_member *member;
> -
> -	member = kmalloc(sizeof(*member), GFP_KERNEL);
> -	if (!member)
> -		return -ENOMEM;
> -
>  	get_dma_buf(dma_buf);
>  	member->dma_buf = dma_buf;
>  	member->handle = handle;
>  	list_add(&member->entry, &prime_fpriv->head);
> -	return 0;
>  }
>  
>  static struct dma_buf *drm_prime_lookup_buf_by_handle(struct drm_prime_file_private *prime_fpriv,
> @@ -409,6 +403,7 @@ int drm_gem_prime_handle_to_fd(struct drm_device *dev,
>  	struct drm_gem_object *obj;
>  	int ret = 0;
>  	struct dma_buf *dmabuf;
> +	struct drm_prime_member *member;
>  
>  	mutex_lock(&file_priv->prime.lock);
>  	obj = drm_gem_object_lookup(dev, file_priv, handle);
> @@ -417,6 +412,12 @@ int drm_gem_prime_handle_to_fd(struct drm_device *dev,
>  		goto out_unlock;
>  	}
>  
> +	member = kmalloc(sizeof(*member), GFP_KERNEL);
> +	if (!member) {
> +		ret = -ENOMEM;
> +		goto out_unlock;
> +	}
> +
>  	dmabuf = drm_prime_lookup_buf_by_handle(&file_priv->prime, handle);
>  	if (dmabuf) {
>  		get_dma_buf(dmabuf);
> @@ -437,6 +438,7 @@ int drm_gem_prime_handle_to_fd(struct drm_device *dev,
>  				 */
>  				ret = PTR_ERR(dmabuf);
>  				mutex_unlock(&dev->object_name_lock);
> +				kfree(member);
>  				goto out;
>  			}
>  		}
> @@ -447,13 +449,9 @@ int drm_gem_prime_handle_to_fd(struct drm_device *dev,
>  		 * protection of dev->object_name_lock to ensure that a racing gem close
>  		 * ioctl doesn't miss to remove this buffer handle from the cache.
>  		 */
> -		ret = drm_prime_add_buf_handle(&file_priv->prime,
> -					       dmabuf, handle);
> +		drm_prime_add_buf_handle(&file_priv->prime,
> +					 member, dmabuf, handle);
>  		mutex_unlock(&dev->object_name_lock);
> -		if (ret) {
> -			dma_buf_put(dmabuf);
> -			goto out;
> -		}
>  	}
>  
>  	ret = dma_buf_fd(dmabuf, flags);
> @@ -560,6 +558,7 @@ int drm_gem_prime_fd_to_handle(struct drm_device *dev,
>  {
>  	struct dma_buf *dma_buf;
>  	struct drm_gem_object *obj;
> +	struct drm_prime_member *member;
>  	int ret;
>  
>  	dma_buf = dma_buf_get(prime_fd);
> @@ -573,6 +572,11 @@ int drm_gem_prime_fd_to_handle(struct drm_device *dev,
>  	if (ret == 0)
>  		goto out_put;
>  
> +	member = kmalloc(sizeof(*member), GFP_KERNEL);
> +	if (!member) {
> +		ret = -ENOMEM;
> +		goto out_put;
> +	}
>  	/* never seen this one, need to import */
>  	mutex_lock(&dev->object_name_lock);
>  	obj = dev->driver->gem_prime_import(dev, dma_buf);
> @@ -595,12 +599,10 @@ int drm_gem_prime_fd_to_handle(struct drm_device *dev,
>  						   obj->dma_buf);
>  	drm_gem_object_unreference_unlocked(obj);
>  	if (ret)
> -		goto out_put;
> +		goto out_member;
>  
> -	ret = drm_prime_add_buf_handle(&file_priv->prime,
> -			dma_buf, *handle);
> -	if (ret)
> -		goto fail;
> +	drm_prime_add_buf_handle(&file_priv->prime,
> +				 member, dma_buf, *handle);

	member = NULL;
>  
>  	mutex_unlock(&file_priv->prime.lock);
>  
> @@ -608,13 +610,10 @@ int drm_gem_prime_fd_to_handle(struct drm_device *dev,
>  
>  	return 0;
>  
> -fail:
> -	/* hmm, if driver attached, we are relying on the free-object path
> -	 * to detach.. which seems ok..
> -	 */
> -	drm_gem_handle_delete(file_priv, *handle);
>  out_unlock:
>  	mutex_unlock(&dev->object_name_lock);
> +out_member:
> +	kfree(member);
>  out_put:

and put the kfree (since it can deal with NULL) below the out_put here as
a random bikeshed. Anyway, looks good as is.

Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>

>  	dma_buf_put(dma_buf);
>  	mutex_unlock(&file_priv->prime.lock);
> -- 
> 2.5.0
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2015-10-15  6:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15  1:51 fix the prime lock deadlock Dave Airlie
2015-10-15  1:51 ` [PATCH 1/4] drm/gem: consolidate handle deletion code Dave Airlie
2015-10-15  1:51 ` [PATCH 2/4] drm/prime: cleanup goto mess in drm_gem_prime_handle_to_fd Dave Airlie
2015-10-15  6:30   ` Daniel Vetter
2015-10-15  1:51 ` [PATCH 3/4] drm/gem: cleanup prime lock issue with drm_gem_handle_create_tail Dave Airlie
2015-10-15  6:36   ` Daniel Vetter
2015-10-15  1:51 ` [PATCH 4/4] drm/prime: cleanup prime/gem locking interaction Dave Airlie
2015-10-15  6:41   ` Daniel Vetter [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=20151015064109.GP26718@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox