All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chunming Zhou <zhoucm1-5C7GfCeVMHo@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/ttm: Always and only destroy bo->ttm_resv in ttm_bo_release_list
Date: Thu, 2 Nov 2017 10:30:21 +0800	[thread overview]
Message-ID: <4ea79938-76b5-cd74-cdb3-3d9c8b56faff@amd.com> (raw)
In-Reply-To: <20171101161529.4844-1-michel-otUistvHUpPR7s880joybQ@public.gmane.org>

I think so, it should be enough we free it in the last place.

We also find many issues for bo->resv and bo->ttm_resv when debugging 
PER-VM-BO feature, after ttm_bo_individualize_resv, we should set 
bo->resv = &bo->ttm_rev before adding to destroy list, and the root resv 
is preventing eviction and swapout. Roger will give a summary and send 
those draft patches.

For this patch, Reviewed-by: Chunming Zhou <david1.zhou@amd.com>


On 2017年11月02日 00:15, Michel Dänzer wrote:
> From: Michel Dänzer <michel.daenzer@amd.com>
>
> Fixes a use-after-free due to a race condition in
> ttm_bo_cleanup_refs_and_unlock, which allows one task to reserve a BO
> and destroy its ttm_resv while another task is waiting for it to signal
> in reservation_object_wait_timeout_rcu.
>
> Fixes: 0d2bd2ae045d "drm/ttm: fix memory leak while individualizing BOs"
> Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
> ---
>   drivers/gpu/drm/ttm/ttm_bo.c | 13 +++----------
>   1 file changed, 3 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
> index 379ec41d2c69..a19a0ebf32ac 100644
> --- a/drivers/gpu/drm/ttm/ttm_bo.c
> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> @@ -150,8 +150,7 @@ static void ttm_bo_release_list(struct kref *list_kref)
>   	ttm_tt_destroy(bo->ttm);
>   	atomic_dec(&bo->glob->bo_count);
>   	dma_fence_put(bo->moving);
> -	if (bo->resv == &bo->ttm_resv)
> -		reservation_object_fini(&bo->ttm_resv);
> +	reservation_object_fini(&bo->ttm_resv);
>   	mutex_destroy(&bo->wu_mutex);
>   	if (bo->destroy)
>   		bo->destroy(bo);
> @@ -406,10 +405,8 @@ static int ttm_bo_individualize_resv(struct ttm_buffer_object *bo)
>   	BUG_ON(!reservation_object_trylock(&bo->ttm_resv));
>   
>   	r = reservation_object_copy_fences(&bo->ttm_resv, bo->resv);
> -	if (r) {
> +	if (r)
>   		reservation_object_unlock(&bo->ttm_resv);
> -		reservation_object_fini(&bo->ttm_resv);
> -	}
>   
>   	return r;
>   }
> @@ -457,10 +454,8 @@ static void ttm_bo_cleanup_refs_or_queue(struct ttm_buffer_object *bo)
>   		if (reservation_object_test_signaled_rcu(&bo->ttm_resv, true)) {
>   			ttm_bo_del_from_lru(bo);
>   			spin_unlock(&glob->lru_lock);
> -			if (bo->resv != &bo->ttm_resv) {
> +			if (bo->resv != &bo->ttm_resv)
>   				reservation_object_unlock(&bo->ttm_resv);
> -				reservation_object_fini(&bo->ttm_resv);
> -			}
>   
>   			ttm_bo_cleanup_memtype_use(bo);
>   			return;
> @@ -560,8 +555,6 @@ static int ttm_bo_cleanup_refs_and_unlock(struct ttm_buffer_object *bo,
>   	}
>   
>   	ttm_bo_del_from_lru(bo);
> -	if (!list_empty(&bo->ddestroy) && (bo->resv != &bo->ttm_resv))
> -		reservation_object_fini(&bo->ttm_resv);
>   	list_del_init(&bo->ddestroy);
>   	kref_put(&bo->list_kref, ttm_bo_ref_bug);
>   

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2017-11-02  2:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 16:15 [PATCH] drm/ttm: Always and only destroy bo->ttm_resv in ttm_bo_release_list Michel Dänzer
     [not found] ` <20171101161529.4844-1-michel-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-11-02  2:30   ` Chunming Zhou [this message]
2017-11-02 10:49   ` Christian König
     [not found]     ` <da4684ab-2c6d-7543-0c5d-3483ca093bc5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-02 17:23       ` Michel Dänzer
2017-11-02 17:22   ` [PATCH v2] " Michel Dänzer
     [not found]     ` <20171102172218.7827-1-michel-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-11-02 17:34       ` Christian König
  -- strict thread matches above, loose matches on Subject: below --
2017-11-01 16:15 [PATCH] " Michel Dänzer

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=4ea79938-76b5-cd74-cdb3-3d9c8b56faff@amd.com \
    --to=zhoucm1-5c7gfcevmho@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=michel-otUistvHUpPR7s880joybQ@public.gmane.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.