linux-kernel - Re: [PATCH v2 09/16] drm/imx: Add i.MX8qxp Display Controller KMS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bb82eb1b-e284-45c4-b80f-7bdb65e0449d@web.de>
Date: Fri, 12 Jul 2024 11:55:24 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Liu Ying <victor.liu@....com>, imx@...ts.linux.dev,
 dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-phy@...ts.infradead.org,
 kernel@...gutronix.de
Cc: LKML <linux-kernel@...r.kernel.org>, Conor Dooley <conor+dt@...nel.org>,
 Daniel Vetter <daniel@...ll.ch>, David Airlie <airlied@...il.com>,
 Dong Aisheng <aisheng.dong@....com>, Fabio Estevam <festevam@...il.com>,
 Francesco Dolcini <francesco@...cini.it>, Frank Li <Frank.Li@....com>,
 Guido Günther <agx@...xcpu.org>,
 Kishon Vijay Abraham I <kishon@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
 Maxime Ripard <mripard@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>,
 Rob Herring <robh@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>,
 Shawn Guo <shawnguo@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
 Thomas Zimmermann <tzimmermann@...e.de>, Vinod Koul <vkoul@...nel.org>
Subject: Re: [PATCH v2 09/16] drm/imx: Add i.MX8qxp Display Controller KMS

…
> +++ b/drivers/gpu/drm/imx/dc/dc-crtc.c
> @@ -0,0 +1,578 @@
…
> +static void dc_crtc_queue_state_event(struct drm_crtc_state *crtc_state)
> +{tglx@...utronix.de
…
> +	spin_lock_irq(&crtc->dev->event_lock);
> +	if (crtc_state->event) {
…
> +	}
> +	spin_unlock_irq(&crtc->dev->event_lock);
> +}
…

Under which circumstances would you become interested to apply a statement
like “guard(spinlock_irq)(&crtc->dev->event_lock);”?
https://elixir.bootlin.com/linux/v6.10-rc7/source/include/linux/spinlock.h#L567

Regards,
Markus