From: Louis Chauvet <louis.chauvet@bootlin.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: Hui Pu <Hui.Pu@gehealthcare.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Ian Ray <ian.ray@gehealthcare.com>
Subject: Re: [PATCH v5 7/7] drm/bridge: prevent encoder chain changes in pre_enable/post_disable
Date: Thu, 9 Apr 2026 11:57:18 +0200 [thread overview]
Message-ID: <4fdc66a6-9429-4c80-8014-a09c492d6cf2@bootlin.com> (raw)
In-Reply-To: <20260324-drm-bridge-alloc-encoder-chain-mutex-v5-7-8bf786c5c7e6@bootlin.com>
On 3/24/26 9:58 AM, Luca Ceresoli wrote:
> Take the encoder chain mutex while iterating over the encoder chain in
> drm_atomic_bridge_chain_pre_enable() and
> drm_atomic_bridge_chain_post_disable() to ensure the lists won't change
> while being inspected.
>
> These functions have nested list_for_each_*() loops, which makes them
> complicated. list_for_each_entry_from() loops could be replaced by
> drm_for_each_bridge_in_chain_from(), but it would not work in a nested way
> in its current implementation. Besides, there is no "_reverse" variant of
> drm_for_each_bridge_in_chain_from().
>
> Keep code simple and readable by explicitly locking around the outer
> loop. Thankfully there are no break or return points inside the loops, so
> the change is trivial and readable.
>
> Reviewed-by: Maxime Ripard <mripard@kernel.org>
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Reviewed-by: Louis Chauvet <louis.chauvet@bootlin.com>
> ---
>
> Changes in v3:
> - Lock encoder->bridge_chain_mutex directly, no wrappers
> - Improved commit message
>
> Changes in v2:
> - Improved commit message
> ---
> drivers/gpu/drm/drm_bridge.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_bridge.c b/drivers/gpu/drm/drm_bridge.c
> index c76f3451af39..29231730e1f8 100644
> --- a/drivers/gpu/drm/drm_bridge.c
> +++ b/drivers/gpu/drm/drm_bridge.c
> @@ -867,6 +867,7 @@ void drm_atomic_bridge_chain_post_disable(struct drm_bridge *bridge,
>
> encoder = bridge->encoder;
>
> + mutex_lock(&encoder->bridge_chain_mutex);
> list_for_each_entry_from(bridge, &encoder->bridge_chain, chain_node) {
> limit = NULL;
>
> @@ -915,6 +916,7 @@ void drm_atomic_bridge_chain_post_disable(struct drm_bridge *bridge,
> /* Jump all bridges that we have already post_disabled */
> bridge = limit;
> }
> + mutex_unlock(&encoder->bridge_chain_mutex);
> }
> EXPORT_SYMBOL(drm_atomic_bridge_chain_post_disable);
>
> @@ -961,6 +963,7 @@ void drm_atomic_bridge_chain_pre_enable(struct drm_bridge *bridge,
>
> encoder = bridge->encoder;
>
> + mutex_lock(&encoder->bridge_chain_mutex);
> list_for_each_entry_reverse(iter, &encoder->bridge_chain, chain_node) {
> if (iter->pre_enable_prev_first) {
> next = iter;
> @@ -1003,6 +1006,7 @@ void drm_atomic_bridge_chain_pre_enable(struct drm_bridge *bridge,
> if (iter == bridge)
> break;
> }
> + mutex_unlock(&encoder->bridge_chain_mutex);
> }
> EXPORT_SYMBOL(drm_atomic_bridge_chain_pre_enable);
>
>
next prev parent reply other threads:[~2026-04-09 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 8:58 [PATCH v5 0/7] drm/bridge: protect encoder bridge chain with a mutex Luca Ceresoli
2026-03-24 8:58 ` [PATCH v5 1/7] drm/encoder: add mutex to protect the bridge chain Luca Ceresoli
2026-04-09 9:56 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 2/7] drm/encoder: drm_encoder_cleanup: lock the encoder chain mutex during removal Luca Ceresoli
2026-04-09 9:55 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 3/7] drm/bridge: drm_bridge_attach: lock the encoder chain mutex during insertion Luca Ceresoli
2026-04-09 9:56 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 4/7] drm/bridge: lock the encoder chain in scoped for_each loops Luca Ceresoli
2026-04-09 9:56 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 5/7] drm/bridge: prevent encoder chain changes while iterating with list_for_each_entry_from() Luca Ceresoli
2026-04-09 9:56 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 6/7] drm/bridge: prevent encoder chain changes while iterating with list_for_each_entry_reverse() Luca Ceresoli
2026-04-09 9:57 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 7/7] drm/bridge: prevent encoder chain changes in pre_enable/post_disable Luca Ceresoli
2026-04-09 9:57 ` Louis Chauvet [this message]
2026-04-16 7:42 ` [PATCH v5 0/7] drm/bridge: protect encoder bridge chain with a mutex Luca Ceresoli
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=4fdc66a6-9429-4c80-8014-a09c492d6cf2@bootlin.com \
--to=louis.chauvet@bootlin.com \
--cc=Hui.Pu@gehealthcare.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ian.ray@gehealthcare.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=thomas.petazzoni@bootlin.com \
--cc=tzimmermann@suse.de \
/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®