From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 2/2] [media] avoid double locks with graph_mutex
Date: Tue, 29 Mar 2016 06:17:34 -0300 [thread overview]
Message-ID: <20160329061734.1a1a5291@recife.lan> (raw)
In-Reply-To: <20160328220642.GD32125@valkosipuli.retiisi.org.uk>
Em Tue, 29 Mar 2016 01:06:42 +0300
Sakari Ailus <sakari.ailus@iki.fi> escreveu:
> Hi Mauro,
>
> Please see my comments below.
>
> On Mon, Mar 28, 2016 at 03:11:04PM -0300, Mauro Carvalho Chehab wrote:
> > Add a note at the headers telling that the link setup
> > callbacks are called with the mutex hold. Also, removes a
> > double lock at the PM suspend callbacks.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> > ---
> > drivers/media/media-device.c | 1 -
> > drivers/media/v4l2-core/v4l2-mc.c | 4 ----
> > include/media/media-device.h | 3 ++-
> > include/media/media-entity.h | 3 +++
> > 4 files changed, 5 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/media/media-device.c b/drivers/media/media-device.c
> > index 6cfa890af7b4..6af5e6932271 100644
> > --- a/drivers/media/media-device.c
> > +++ b/drivers/media/media-device.c
> > @@ -93,7 +93,6 @@ static struct media_entity *find_entity(struct media_device *mdev, u32 id)
> > media_device_for_each_entity(entity, mdev) {
> > if (((media_entity_id(entity) == id) && !next) ||
> > ((media_entity_id(entity) > id) && next)) {
> > - mutex_unlock(&mdev->graph_mutex);
>
> Unrelated to this patch.
Yes. This belongs to patch 1.
>
> Please do also consider compat IOCTL handling code.
>
> > return entity;
> > }
> > }
> > diff --git a/drivers/media/v4l2-core/v4l2-mc.c b/drivers/media/v4l2-core/v4l2-mc.c
> > index 2228cd3a846e..d44ff2ec314f 100644
> > --- a/drivers/media/v4l2-core/v4l2-mc.c
> > +++ b/drivers/media/v4l2-core/v4l2-mc.c
> > @@ -348,8 +348,6 @@ int v4l2_pipeline_pm_use(struct media_entity *entity, int use)
> > int change = use ? 1 : -1;
> > int ret;
> >
> > - mutex_lock(&mdev->graph_mutex);
>
> What's the motivation for this change and the one below?
>
> As far as I can see, they remove access serialisation of graph state during
> graph walk, which certainly is not the right thing to do.
You're right. This is not correct. I was thinking that v4l2_pipeline_pm_use()
was called by v4l2_pipeline_link_notify(), but this is not the case. The
function called there is pipeline_pm_use_count(), with doesn't hold the mutex.
> > -
> > /* Apply use count to node. */
> > entity->use_count += change;
> > WARN_ON(entity->use_count < 0);
> > @@ -359,8 +357,6 @@ int v4l2_pipeline_pm_use(struct media_entity *entity, int use)
> > if (ret < 0)
> > entity->use_count -= change;
> >
> > - mutex_unlock(&mdev->graph_mutex);
> > -
> > return ret;
> > }
> > EXPORT_SYMBOL_GPL(v4l2_pipeline_pm_use);
> > diff --git a/include/media/media-device.h b/include/media/media-device.h
> > index b04cfa907350..e6ad30c323fc 100644
> > --- a/include/media/media-device.h
> > +++ b/include/media/media-device.h
> > @@ -312,7 +312,8 @@ struct media_entity_notify {
> > * @enable_source: Enable Source Handler function pointer
> > * @disable_source: Disable Source Handler function pointer
> > *
> > - * @link_notify: Link state change notification callback
> > + * @link_notify: Link state change notification callback. This callback is
> > + * Called with the graph_mutex hold.
>
> I don't mind adding documentation such as this, but I'd put it into a
> separate patch.
Ok. Patch 2 will be just a documentation patch. I'll resend the series in
a few.
>
> > *
> > * This structure represents an abstract high-level media device. It allows easy
> > * access to entities and provides basic media device-level support. The
> > diff --git a/include/media/media-entity.h b/include/media/media-entity.h
> > index 6dc9e4e8cbd4..0b16ebe36db7 100644
> > --- a/include/media/media-entity.h
> > +++ b/include/media/media-entity.h
> > @@ -179,6 +179,9 @@ struct media_pad {
> > * @link_validate: Return whether a link is valid from the entity point of
> > * view. The media_entity_pipeline_start() function
> > * validates all links by calling this operation. Optional.
> > + *
> > + * Note: Those ioctls should not touch the struct media_device.@graph_mutex
> > + * field, as they're called with it already hold.
> > */
> > struct media_entity_operations {
> > int (*link_setup)(struct media_entity *entity,
>
--
Thanks,
Mauro
next prev parent reply other threads:[~2016-03-29 9:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 22:22 [PATCH 0/2] media: Revert broken locking changes Laurent Pinchart
2016-03-24 22:22 ` [PATCH 1/2] Revert "[media] media-device: use kref for media_device instance" Laurent Pinchart
2016-03-24 22:22 ` [PATCH 2/2] Revert "[media] media-device: get rid of the spinlock" Laurent Pinchart
2016-03-28 18:09 ` [PATCH 0/2] media: Revert broken locking changes Mauro Carvalho Chehab
2016-03-28 18:11 ` [PATCH 1/2] [media] media-device: Fix mutex handling code for ioctl Mauro Carvalho Chehab
2016-03-28 18:11 ` [PATCH 2/2] [media] avoid double locks with graph_mutex Mauro Carvalho Chehab
2016-03-28 19:38 ` Javier Martinez Canillas
2016-03-28 22:06 ` Sakari Ailus
2016-03-29 9:17 ` Mauro Carvalho Chehab [this message]
2016-03-29 9:28 ` Mauro Carvalho Chehab
2016-03-29 9:38 ` Sakari Ailus
2016-03-28 21:58 ` [PATCH 1/2] [media] media-device: Fix mutex handling code for ioctl Sakari Ailus
2016-03-29 9:07 ` Mauro Carvalho Chehab
2016-03-28 19:28 ` [PATCH 0/2] media: Revert broken locking changes Javier Martinez Canillas
2016-03-28 19:29 ` Laurent Pinchart
2016-03-28 20:15 ` Mauro Carvalho Chehab
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=20160329061734.1a1a5291@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sakari.ailus@iki.fi \
--cc=shuahkh@osg.samsung.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