mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 6/7] drm/bridge: prevent encoder chain changes while iterating with list_for_each_entry_reverse()
Date: Thu, 9 Apr 2026 11:57:09 +0200	[thread overview]
Message-ID: <9e517e8d-f944-4934-9f97-07101ec98711@bootlin.com> (raw)
In-Reply-To: <20260324-drm-bridge-alloc-encoder-chain-mutex-v5-6-8bf786c5c7e6@bootlin.com>



On 3/24/26 9:58 AM, Luca Ceresoli wrote:
> These loops in drm_bridge.c iterate over the encoder chain using
> list_for_each_entry_reverse(), which does not prevent changes to the bridge
> chain while iterating over it.
> 
> Take the encoder chain mutex while iterating to avoid chain changes while
> iterating.
> 
> All the "simple" loops are converted. drm_atomic_bridge_chain_pre_enable()
> and drm_atomic_bridge_chain_post_disable() are handled by a separate
> commit.
> 
> 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
> 
> Changes in v2: none
> ---
>   drivers/gpu/drm/drm_bridge.c | 40 ++++++++++++++++++++++------------------
>   1 file changed, 22 insertions(+), 18 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_bridge.c b/drivers/gpu/drm/drm_bridge.c
> index 37feb8143de4..c76f3451af39 100644
> --- a/drivers/gpu/drm/drm_bridge.c
> +++ b/drivers/gpu/drm/drm_bridge.c
> @@ -808,6 +808,7 @@ void drm_atomic_bridge_chain_disable(struct drm_bridge *bridge,
>   		return;
>   
>   	encoder = bridge->encoder;
> +	mutex_lock(&encoder->bridge_chain_mutex);
>   	list_for_each_entry_reverse(iter, &encoder->bridge_chain, chain_node) {
>   		if (iter->funcs->atomic_disable) {
>   			iter->funcs->atomic_disable(iter, state);
> @@ -818,6 +819,7 @@ void drm_atomic_bridge_chain_disable(struct drm_bridge *bridge,
>   		if (iter == bridge)
>   			break;
>   	}
> +	mutex_unlock(&encoder->bridge_chain_mutex);
>   }
>   EXPORT_SYMBOL(drm_atomic_bridge_chain_disable);
>   
> @@ -1322,25 +1324,27 @@ int drm_atomic_bridge_chain_check(struct drm_bridge *bridge,
>   		return ret;
>   
>   	encoder = bridge->encoder;
> -	list_for_each_entry_reverse(iter, &encoder->bridge_chain, chain_node) {
> -		int ret;
> -
> -		/*
> -		 * Bus flags are propagated by default. If a bridge needs to
> -		 * tweak the input bus flags for any reason, it should happen
> -		 * in its &drm_bridge_funcs.atomic_check() implementation such
> -		 * that preceding bridges in the chain can propagate the new
> -		 * bus flags.
> -		 */
> -		drm_atomic_bridge_propagate_bus_flags(iter, conn,
> -						      crtc_state->state);
> -
> -		ret = drm_atomic_bridge_check(iter, crtc_state, conn_state);
> -		if (ret)
> -			return ret;
> +	scoped_guard(mutex, &encoder->bridge_chain_mutex) {
> +		list_for_each_entry_reverse(iter, &encoder->bridge_chain, chain_node) {
> +			int ret;
> +
> +			/*
> +			 * Bus flags are propagated by default. If a bridge needs to
> +			 * tweak the input bus flags for any reason, it should happen
> +			 * in its &drm_bridge_funcs.atomic_check() implementation such
> +			 * that preceding bridges in the chain can propagate the new
> +			 * bus flags.
> +			 */
> +			drm_atomic_bridge_propagate_bus_flags(iter, conn,
> +							      crtc_state->state);
> +
> +			ret = drm_atomic_bridge_check(iter, crtc_state, conn_state);
> +			if (ret)
> +				return ret;
>   
> -		if (iter == bridge)
> -			break;
> +			if (iter == bridge)
> +				break;
> +		}
>   	}
>   
>   	return 0;
> 


  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 [this message]
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
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=9e517e8d-f944-4934-9f97-07101ec98711@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®