From: "Christian König" <christian.koenig@amd.com>
To: zhanglianjie <zhanglianjie@uniontech.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
PanXinhui <Xinhui.Pan@amd.com>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] drm/radeon/uvd: Fix forgotten unmap buffer objects
Date: Tue, 8 Feb 2022 09:33:14 +0100 [thread overview]
Message-ID: <00c5b899-ed35-44a0-6b22-bc3e882e49d4@amd.com> (raw)
In-Reply-To: <400b7279-b738-5614-dff7-0e2f6f395a0e@uniontech.com>
I think so, Alex will probably pick that up.
Thanks,
Christian.
Am 08.02.22 um 09:28 schrieb zhanglianjie:
> I am very sorry that I submitted many times due to the character
> coding problem. Can PATCH V4 be used?
>
>> I'm scratching my head what you are doing here?
>>
>> That's the fives time you send out the same patch, so something is
>> going wrong here :)
>>
>> Please double check why that lands in your outbox over and over again.
>>
>> Regards,
>> Christian.
>>
>> Am 08.02.22 um 09:14 schrieb zhanglianjie:
>>> after the buffer object is successfully mapped, call
>>> radeon_bo_kunmap before the function returns.
>>>
>>> Signed-off-by: zhanglianjie <zhanglianjie@uniontech.com>
>>> Reviewed-by: Christian König <christian.koenig@amd.com>
>>>
>>> diff --git a/drivers/gpu/drm/radeon/radeon_uvd.c
>>> b/drivers/gpu/drm/radeon/radeon_uvd.c
>>> index 377f9cdb5b53..0558d928d98d 100644
>>> --- a/drivers/gpu/drm/radeon/radeon_uvd.c
>>> +++ b/drivers/gpu/drm/radeon/radeon_uvd.c
>>> @@ -497,6 +497,7 @@ static int radeon_uvd_cs_msg(struct
>>> radeon_cs_parser *p, struct radeon_bo *bo,
>>> handle = msg[2];
>>>
>>> if (handle == 0) {
>>> + radeon_bo_kunmap(bo);
>>> DRM_ERROR("Invalid UVD handle!\n");
>>> return -EINVAL;
>>> }
>>> @@ -559,12 +560,10 @@ static int radeon_uvd_cs_msg(struct
>>> radeon_cs_parser *p, struct radeon_bo *bo,
>>> return 0;
>>>
>>> default:
>>> -
>>> DRM_ERROR("Illegal UVD message type (%d)!\n", msg_type);
>>> - return -EINVAL;
>>> }
>>>
>>> - BUG();
>>> + radeon_bo_kunmap(bo);
>>> return -EINVAL;
>>> }
>>>
>>> --
>>> 2.20.1
>>>
>>>
>>>
>>
>>
>
>
>
next prev parent reply other threads:[~2022-02-08 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 8:14 zhanglianjie
2022-02-08 8:17 ` Christian König
[not found] ` <400b7279-b738-5614-dff7-0e2f6f395a0e@uniontech.com>
2022-02-08 8:33 ` Christian König [this message]
2022-02-08 17:37 ` 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=00c5b899-ed35-44a0-6b22-bc3e882e49d4@amd.com \
--to=christian.koenig@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhanglianjie@uniontech.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
all inboxes | Powered by JetHome®