From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/amdgpu: fix missing dma_fence_put in error path
Date: Thu, 5 Jan 2023 20:11:19 +0100 [thread overview]
Message-ID: <314b034f-e152-90b4-ce98-f5692f72de79@gmail.com> (raw)
In-Reply-To: <CADnq5_OdokG3VZxp0FE-zbvBoLiZcWQkxhcHCwa7ZMCvx2FkOw@mail.gmail.com>
Am 05.01.23 um 17:50 schrieb Alex Deucher:
> On Thu, Jan 5, 2023 at 6:17 AM Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> When the fence can't be added we need to drop the reference.
>>
>> Suggested-by: Bert Karwatzki <spasswolf@web.de>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
> please add:
> Cc: stable@vger.kernel.org # 6.1.x
> When you push this series.
But none of this is in 6.1? That are pure 6.2 changes or am I missing
something?
Christian.
>
> Alex
>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c
>> index bac7976975bd..dcd8c066bc1f 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c
>> @@ -391,8 +391,10 @@ int amdgpu_sync_push_to_job(struct amdgpu_sync *sync, struct amdgpu_job *job)
>>
>> dma_fence_get(f);
>> r = drm_sched_job_add_dependency(&job->base, f);
>> - if (r)
>> + if (r) {
>> + dma_fence_put(f);
>> return r;
>> + }
>> }
>> return 0;
>> }
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2023-01-05 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 11:17 [PATCH 1/2] drm/amdgpu: fix another missing fence reference in the CS code Christian König
2023-01-05 11:17 ` [PATCH 2/2] drm/amdgpu: fix missing dma_fence_put in error path Christian König
2023-01-05 14:35 ` Alex Deucher
2023-01-05 16:12 ` Luben Tuikov
2023-01-05 16:50 ` Alex Deucher
2023-01-05 19:11 ` Christian König [this message]
2023-01-05 19:26 ` Alex Deucher
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=314b034f-e152-90b4-ce98-f5692f72de79@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@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.