From: "Nicolai Hähnle" <nhaehnle-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Christian König"
<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>,
"Nicolai Hähnle"
<nhaehnle-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH 1/2] drm/ttm: never add BO that failed to validate to the LRU list
Date: Tue, 14 Feb 2017 12:37:44 +0100 [thread overview]
Message-ID: <3ac4923c-61b9-8ee9-e9cb-d7a60fc51dbf@gmail.com> (raw)
In-Reply-To: <ef1d2448-4296-5eaf-a852-5000bd16a947-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
On 14.02.2017 11:38, Christian König wrote:
> Am 14.02.2017 um 10:18 schrieb Nicolai Hähnle:
>> From: Nicolai Hähnle <nicolai.haehnle@amd.com>
>>
>> Fixes a potential race condition in amdgpu that looks as follows:
>>
>> Task 1: attempt ttm_bo_init, but ttm_bo_validate fails
>> Task 1: add BO to global list anyway
>> Task 2: grabs hold of the BO, waits on its reservation lock
>> Task 1: releases its reference of the BO; never gives up the
>> reservation lock
>>
>> The patch "drm/amdgpu: fix a potential deadlock in
>> amdgpu_bo_create_restricted()" attempts to fix that by releasing
>> the reservation lock in amdgpu code; unfortunately, it introduces
>> a use-after-free when this race _doesn't_ happen.
>>
>> This patch should fix the race properly by never adding the BO
>> to the global list in the first place.
>>
>> Cc: Samuel Pitoiset <samuel.pitoiset@gmail.com>
>> Cc: zhoucm1 <david1.zhou@amd.com>
>> Signed-off-by: Nicolai Hähnle <nicolai.haehnle@amd.com>
>
> NAK, that is actually not correct either.
>
> The previous implementation doesn't have an use after free, but actually
> a memory leak.
>
> I completely agree that adding the BO to the LRU in case of an error is
> incorrect, but ttm_bo_add_to_lru() will add some references to the BO.
Yes, but those are bo->list_krefs, not bo->krefs. ttm_bo_unref will put
the bo->kref, which should lead to ttm_bo_release. This will then add
the buffer to the ddestroy list and eventually put all the list_krefs.
(Or possibly, if the ttm_bo_wait in ttm_bo_cleanup_refs_or_queue fails,
it will explicitly delete the buffer from the LRU, which should amount
to the same, I think).
Or perhaps I'm still missing something, I'm not too familiar with the
whole BO reference counting.
> So the following ttm_bo_unref() will just drop the initial reference.
>
> Let's clean up this mess by moving the freeing of the BO in case of an
> error to the caller.
Yes, see my other patches.
Thanks,
Nicolai
>
> Regards,
> Christian.
>
>> ---
>> drivers/gpu/drm/ttm/ttm_bo.c | 12 +++++++-----
>> 1 file changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
>> index 239a957..76bee42 100644
>> --- a/drivers/gpu/drm/ttm/ttm_bo.c
>> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
>> @@ -1215,18 +1215,20 @@ int ttm_bo_init(struct ttm_bo_device *bdev,
>> if (likely(!ret))
>> ret = ttm_bo_validate(bo, placement, interruptible, false);
>> - if (!resv) {
>> + if (!resv)
>> ttm_bo_unreserve(bo);
>> - } else if (!(bo->mem.placement & TTM_PL_FLAG_NO_EVICT)) {
>> + if (unlikely(ret)) {
>> + ttm_bo_unref(&bo);
>> + return ret;
>> + }
>> +
>> + if (resv && !(bo->mem.placement & TTM_PL_FLAG_NO_EVICT)) {
>> spin_lock(&bo->glob->lru_lock);
>> ttm_bo_add_to_lru(bo);
>> spin_unlock(&bo->glob->lru_lock);
>> }
>> - if (unlikely(ret))
>> - ttm_bo_unref(&bo);
>> -
>> return ret;
>> }
>> EXPORT_SYMBOL(ttm_bo_init);
>
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-02-14 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 9:18 [PATCH 0/2] drm/ttm, amdgpu: fix use-after-free in recent deadlock fix Nicolai Hähnle
2017-02-14 9:18 ` [PATCH 2/2] Revert "drm/amdgpu: fix a potential deadlock in amdgpu_bo_create_restricted()" Nicolai Hähnle
[not found] ` <20170214091845.1225-1-nhaehnle-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-14 9:18 ` [PATCH 1/2] drm/ttm: never add BO that failed to validate to the LRU list Nicolai Hähnle
2017-02-14 10:38 ` Christian König
[not found] ` <ef1d2448-4296-5eaf-a852-5000bd16a947-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-02-14 11:37 ` Nicolai Hähnle [this message]
[not found] ` <3ac4923c-61b9-8ee9-e9cb-d7a60fc51dbf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-14 12:53 ` Christian König
2017-02-14 10:10 ` [PATCH 0/2] drm/ttm, amdgpu: fix use-after-free in recent deadlock fix Samuel Pitoiset
2017-02-14 11:11 ` Samuel Pitoiset
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=3ac4923c-61b9-8ee9-e9cb-d7a60fc51dbf@gmail.com \
--to=nhaehnle-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox