From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Race in rcar-v4l2.c
Date: Fri, 6 Sep 2024 12:14:46 +0200 [thread overview]
Message-ID: <20240906101446.GS3708622@fsdn.se> (raw)
In-Reply-To: <af3f0b7c-d184-4b2e-bb75-6349ef32e4c3@ideasonboard.com>
Hi Tomi,
Thanks for your report.
I have an on-going series trying to clean this all up [1]. The one
change in the v4l-async core I proposed was however rejected and I have
yet to circle back to figure out a different solution.
Could you give it a try and see if it also solves this issue?
1. [PATCH 0/6] media: rcar-vin: Make use of multiple connections in v4l-async
https://lore.kernel.org/linux-renesas-soc/20240129202254.1126012-1-niklas.soderlund+renesas@ragnatech.se/
On 2024-09-06 12:57:50 +0300, Tomi Valkeinen wrote:
> Hi Niklas,
>
> There seems to be a race in rcar-v4l2.c, causing
> WARN_ON(entity->use_count < 0) in pipeline_pm_power_one().
>
> If my understanding is correct, the VIN v4l2 nodes are being created
> (rvin_v4l2_register), meaning they are userspace accessible, but the media
> pipeline as a whole is not ready yet (e.g. media links).
>
> So what happens is that after some video nodes have been created, the
> userspace opens them (I think it's udevd checking the new device nodes),
> causing rvin_open(). rvin_open() goes through the media graph and does some
> PM enabling (I'm not familiar with the legacy v4l2_pipeline_pm_get()).
> However, as the links are not there, it doesn't really enable much at all.
>
> Then the driver goes forward and finishes with the media graph.
>
> Then the userspace closes the opened video nodes, rvin_release() gets called
> and it goes through the media graph, which now contains all the entities,
> and powers them down. As the entities were never powered up, we hit the
> use_count warning.
>
> This happens quite often to me when loading the modules, but I think it can
> be made to happen more often by adding msleep(1000) to the beginning of
> rvin_release(), thus ensuring that the graph setup is finished before the
> rvin_release() proceeds (and hoping that the graph setup was not ready when
> rvin_open() was called).
>
> Tomi
>
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2024-09-06 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 9:57 Race in rcar-v4l2.c Tomi Valkeinen
2024-09-06 10:14 ` Niklas Söderlund [this message]
2024-09-06 11:14 ` Tomi Valkeinen
2024-09-06 11:27 ` Tomi Valkeinen
2024-09-06 12:28 ` Tomi Valkeinen
2024-09-06 13:46 ` Niklas Söderlund
2024-09-06 14:13 ` Tomi Valkeinen
2024-09-06 15:18 ` Niklas Söderlund
2024-09-06 15:45 ` Tomi Valkeinen
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=20240906101446.GS3708622@fsdn.se \
--to=niklas.soderlund@ragnatech.se \
--cc=linux-media@vger.kernel.org \
--cc=tomi.valkeinen@ideasonboard.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 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.