From: Julia Lawall <julia.lawall@lip6.fr>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/sysfs: Grab lock for edid/modes_show
Date: Fri, 2 Oct 2015 17:02:48 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1510021702270.2634@hadrien> (raw)
In-Reply-To: <1443775171-31600-1-git-send-email-daniel.vetter@ffwll.ch>
On Fri, 2 Oct 2015, Daniel Vetter wrote:
> We chase pointers/lists without taking the locks protecting them,
> which isn't that good.
>
> Fix it.
>
> v2: Actually unlock properly, spotted by Julia.
The unlock is still on top of the unlock label?
julia
>
> Cc: Julia Lawall <julia.lawall@lip6.fr>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
> drivers/gpu/drm/drm_sysfs.c | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_sysfs.c b/drivers/gpu/drm/drm_sysfs.c
> index 7506de0a75b4..9bffa63fe849 100644
> --- a/drivers/gpu/drm/drm_sysfs.c
> +++ b/drivers/gpu/drm/drm_sysfs.c
> @@ -261,23 +261,29 @@ static ssize_t edid_show(struct file *filp, struct kobject *kobj,
> struct drm_connector *connector = to_drm_connector(connector_dev);
> unsigned char *edid;
> size_t size;
> + ssize_t ret = 0;
>
> + mutex_lock(&connector->dev->mode_config.mutex);
> if (!connector->edid_blob_ptr)
> - return 0;
> + goto unlock;
>
> edid = connector->edid_blob_ptr->data;
> size = connector->edid_blob_ptr->length;
> if (!edid)
> - return 0;
> + goto unlock;
>
> if (off >= size)
> - return 0;
> + goto unlock;
>
> if (off + count > size)
> count = size - off;
> memcpy(buf, edid + off, count);
>
> - return count;
> + ret = count;
> + mutex_unlock(&connector->dev->mode_config.mutex);
> +unlock:
> +
> + return ret;
> }
>
> static ssize_t modes_show(struct device *device,
> @@ -288,10 +294,12 @@ static ssize_t modes_show(struct device *device,
> struct drm_display_mode *mode;
> int written = 0;
>
> + mutex_lock(&connector->dev->mode_config.mutex);
> list_for_each_entry(mode, &connector->modes, head) {
> written += snprintf(buf + written, PAGE_SIZE - written, "%s\n",
> mode->name);
> }
> + mutex_unlock(&connector->dev->mode_config.mutex);
>
> return written;
> }
> --
> 2.5.1
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-02 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 7:37 [PATCH] drm: Fix locking for sysfs dpms file Daniel Vetter
2015-09-29 7:56 ` Daniel Vetter
2015-09-29 13:30 ` Jani Nikula
2015-09-29 14:37 ` Jens Axboe
2015-09-29 8:06 ` [PATCH 1/3] drm/sysfs: Annote lockless show functions with READ_ONCE Daniel Vetter
2015-09-29 8:06 ` [PATCH 2/3] drm/sysfs: Grab lock for edid/modes_show Daniel Vetter
2015-10-02 8:39 ` [PATCH] " Daniel Vetter
2015-10-02 11:01 ` Daniel Vetter
2015-10-02 12:08 ` Emil Velikov
2015-11-19 16:22 ` Daniel Vetter
2015-10-02 15:02 ` Julia Lawall [this message]
2015-09-29 8:06 ` [PATCH 3/3] drm/sysfs: Nuke TV/DVI property files Daniel Vetter
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=alpine.DEB.2.10.1510021702270.2634@hadrien \
--to=julia.lawall@lip6.fr \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).