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 2/7] drm/encoder: drm_encoder_cleanup: lock the encoder chain mutex during removal
Date: Thu, 9 Apr 2026 11:55:52 +0200	[thread overview]
Message-ID: <c39ff288-8e29-43e0-b392-a5532114f5c3@bootlin.com> (raw)
In-Reply-To: <20260324-drm-bridge-alloc-encoder-chain-mutex-v5-2-8bf786c5c7e6@bootlin.com>



On 3/24/26 9:58 AM, Luca Ceresoli wrote:
> drm_encoder_cleanup() modifies the encoder chain by removing bridges via
> drm_bridge_detach(). Protect this whole operation by taking the mutex, so
> that:
> 
>   * any users iterating over the chain will not access it during the change
>   * other code willing to modify the list (drm_bridge_attach()) will wait
>     until drm_encoder_cleanup() is done
> 
> Note that the _safe macro in use here is providing a different and
> orthogonal kind of protection than the mutex:
> 
>   1. list_for_each_entry_safe() allows removing the current entry from the
>      list it is iterating on, synchronously; the non-safe version would be
>      unable to find the next entry after the current entry has been removed
>   2. the mutex being added allows to ensure that the list is not used
>      asynchronously by other code while it is being modified; this prevents
>      such other concurrent code to derail because it is iterating over an
>      element while it is removed
> 
> The _safe macro, which works by taking the "next" pointer in addition to
> the "current" one, does not even try to provide the protection at item 2
> above. This is visible e.g. when the "next" element is removed by other
> concurrent code. This is what would happen without the added mutex:
> 
>   1. start loop: list_for_each_entry_safe(pos, n, ...) sets:
>      pos = list_first_entry()   = (bridge 1)
>      n   = list_next_entry(pos) = (bridge 2)
>   2. enter the loop 1st time, do something with *pos (bridge 1)
>   3. in the meanwhile bridge 2 is hot-unplugged
>      -> another thread removes bridge 2
>         -> drm_bridge_detach()
>            -> list_del() sets (bridge 2)->next = LIST_POISON1
>   4. loop iteration 1 finishes, list_for_each_entry_safe() sets:
>      pos = n (previously set to bridge 2)
>      n   = (bridge 2)->next = LIST_POISON1
>   5. enter the loop 2nd time, do something with *pos (bridge 2)
>   6. loop iteration 2 finishes, list_for_each_entry_safe() sets:
>      pos = n = LIST_POISON1 ==> bug!
> 
> However, simply adding mutex_[un]lock(&encoder->bridge_chain_mutex)
> before/after the list_for_each_entry_safe() seems a simple and good
> solution, but it is introducing a possible ABBA deadlock (found by
> PROVE_LOCKING). The two code paths involved are:
> 
>   * drm_encoder_cleanup():
>     - takes the bridge_chain_mutex (A)
>     - calls drm_bridge_detach -> drm_atomic_private_obj_fini ->
>       DRM_MODESET_LOCK_ALL_BEGIN() which takes all locks in the
>       acquisition context (B)
>   * drm_mode_getconnector() (and other code paths):
>     - calls drm_helper_probe_single_connector_modes() which:
>       - takes a drm_modeset_lock in the acquisition context (B)
>       - calls __drm_helper_update_and_validate ->
>         drm_bridge_chain_mode_valid -> drm_for_each_bridge_in_chain_from()
>         which takes the bridge_chain_mutex (A)
> 
> To avoid this potential ABBA deadlock, move all list items to a temporary
> list while holding the bridge_chain_mutex, then detach all elements from
> the temporary list without the mutex.
> 
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

Reviewed-by: Louis Chauvet <louis.chauvet@bootlin.com>

> 
> ---
> 
> Changes in v5:
> - Small commit message improvement
> 
> Changes in v3:
> - Prevent ABBA deadlock by using a temporary list
> - Improve commit message
> 
> Changes in v2:
> - Expanded commit messge with rationale, as discussed
> ---
>   drivers/gpu/drm/drm_encoder.c | 16 ++++++++++++++--
>   1 file changed, 14 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_encoder.c b/drivers/gpu/drm/drm_encoder.c
> index 3261f142baea..0d5dbed06db4 100644
> --- a/drivers/gpu/drm/drm_encoder.c
> +++ b/drivers/gpu/drm/drm_encoder.c
> @@ -189,14 +189,26 @@ void drm_encoder_cleanup(struct drm_encoder *encoder)
>   {
>   	struct drm_device *dev = encoder->dev;
>   	struct drm_bridge *bridge, *next;
> +	LIST_HEAD(tmplist);
>   
>   	/* Note that the encoder_list is considered to be static; should we
>   	 * remove the drm_encoder at runtime we would have to decrement all
>   	 * the indices on the drm_encoder after us in the encoder_list.
>   	 */
>   
> -	list_for_each_entry_safe(bridge, next, &encoder->bridge_chain,
> -				 chain_node)
> +	/*
> +	 * We need the bridge_chain_mutex to modify the chain, but
> +	 * drm_bridge_detach() will call DRM_MODESET_LOCK_ALL_BEGIN() (in
> +	 * drm_modeset_lock_fini()), resulting in a possible ABBA circular
> +	 * deadlock. Avoid it by first moving all the bridges to a
> +	 * temporary list holding the lock, and then calling
> +	 * drm_bridge_detach() without the lock.
> +	 */
> +	mutex_lock(&encoder->bridge_chain_mutex);
> +	list_cut_before(&tmplist, &encoder->bridge_chain, &encoder->bridge_chain);
> +	mutex_unlock(&encoder->bridge_chain_mutex);
> +
> +	list_for_each_entry_safe(bridge, next, &tmplist, chain_node)
>   		drm_bridge_detach(bridge);
>   
>   	drm_mode_object_unregister(dev, &encoder->base);
> 


  reply	other threads:[~2026-04-09  9:56 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 [this message]
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
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=c39ff288-8e29-43e0-b392-a5532114f5c3@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®