From: Melissa Wen <mwen@igalia.com>
To: Yongzhi Liu <lyz_cs@pku.edu.cn>
Cc: emma@anholt.net, airlied@linux.ie, daniel@ffwll.ch,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/v3d: fix missing unlock
Date: Fri, 28 Jan 2022 11:55:10 -0100 [thread overview]
Message-ID: <20220128125510.idyai4bp3g5nbzd2@mail.igalia.com> (raw)
In-Reply-To: <1643278460-100473-1-git-send-email-lyz_cs@pku.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]
On 01/27, Yongzhi Liu wrote:
> [why]
> Unlock is needed on the error handling path to prevent dead lock.
> v3d_submit_cl_ioctl and v3d_submit_csd_ioctl is missing unlock.
>
> [how]
> Fix this by change goto target on the error handling path.
s/change/changing/g
I would just say: `Changing the goto to target an error handling path
that includes drm_gem_unlock reservations.`
and drop the explanation below
> As unlock is handle in fail_unreserve, i keep the failures
> handling around there. So the goto targets a place between
> `fail_unreserve:` and `fail:`.
>
> Signed-off-by: Yongzhi Liu <lyz_cs@pku.edu.cn>
> ---
> drivers/gpu/drm/v3d/v3d_gem.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/v3d/v3d_gem.c b/drivers/gpu/drm/v3d/v3d_gem.c
> index c7ed2e1..d9c7b39 100644
> --- a/drivers/gpu/drm/v3d/v3d_gem.c
> +++ b/drivers/gpu/drm/v3d/v3d_gem.c
> @@ -798,7 +798,7 @@ v3d_submit_cl_ioctl(struct drm_device *dev, void *data,
>
> if (!render->base.perfmon) {
> ret = -ENOENT;
> - goto fail;
> + goto v3d_unlock;
We usually use a `fail` prefix when handling failures.
A suggestion: `fail_perfmon` ?
> }
> }
>
> @@ -847,6 +847,7 @@ v3d_submit_cl_ioctl(struct drm_device *dev, void *data,
>
> fail_unreserve:
> mutex_unlock(&v3d->sched_lock);
> +v3d_unlock:
> drm_gem_unlock_reservations(last_job->bo,
> last_job->bo_count, &acquire_ctx);
> fail:
> @@ -1027,7 +1028,7 @@ v3d_submit_csd_ioctl(struct drm_device *dev, void *data,
> args->perfmon_id);
> if (!job->base.perfmon) {
> ret = -ENOENT;
> - goto fail;
> + goto v3d_unlock;
> }
> }
>
> @@ -1056,6 +1057,7 @@ v3d_submit_csd_ioctl(struct drm_device *dev, void *data,
>
> fail_unreserve:
> mutex_unlock(&v3d->sched_lock);
> +v3d_unlock:
> drm_gem_unlock_reservations(clean_job->bo, clean_job->bo_count,
> &acquire_ctx);
> fail:
With these changes, you can include in the next version my r-b:
Reviewed-by: Melissa Wen <mwen@igalia.com>
> --
> 2.7.4
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-28 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 16:26 [PATCH] drm/v3d: Add " Yongzhi Liu
2022-01-26 20:57 ` Melissa Wen
2022-01-27 10:14 ` [PATCH v2] drm/v3d: fix " Yongzhi Liu
2022-01-28 12:55 ` Melissa Wen [this message]
2022-01-28 13:41 ` [PATCH v3] " Yongzhi Liu
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=20220128125510.idyai4bp3g5nbzd2@mail.igalia.com \
--to=mwen@igalia.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lyz_cs@pku.edu.cn \
/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®