[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACvgo53u01BK_D0ZssV+gCepjxSz23Nr5Dy1qXeaAoJuu6VCFQ@mail.gmail.com>
Date: Tue, 15 Feb 2022 12:04:39 +0000
From: Emil Velikov <emil.l.velikov@...il.com>
To: Hsin-Yi Wang <hsinyi@...omium.org>
Cc: ML dri-devel <dri-devel@...ts.freedesktop.org>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
amd-gfx mailing list <amd-gfx@...ts.freedesktop.org>,
Intel Graphics Development <intel-gfx@...ts.freedesktop.org>,
Chun-Kuang Hu <chunkuang.hu@...nel.org>,
devicetree <devicetree@...r.kernel.org>,
Simon Ser <contact@...rsion.fr>,
"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
Maxime Ripard <mripard@...nel.org>,
Alex Deucher <alexander.deucher@....com>,
Rob Herring <robh+dt@...nel.org>,
linux-mediatek@...ts.infradead.org,
Thomas Zimmermann <tzimmermann@...e.de>,
Harry Wentland <harry.wentland@....com>,
Matthias Brugger <matthias.bgg@...il.com>,
LAKML <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [Intel-gfx] [PATCH v8 1/3] gpu: drm: separate panel orientation
property creating and value setting
Greetings everyone,
Padron for joining in so late o/
On Tue, 8 Feb 2022 at 08:42, Hsin-Yi Wang <hsinyi@...omium.org> wrote:
>
> drm_dev_register() sets connector->registration_state to
> DRM_CONNECTOR_REGISTERED and dev->registered to true. If
> drm_connector_set_panel_orientation() is first called after
> drm_dev_register(), it will fail several checks and results in following
> warning.
>
> Add a function to create panel orientation property and set default value
> to UNKNOWN, so drivers can call this function to init the property earlier
> , and let the panel set the real value later.
>
The warning illustrates a genuine race condition, where userspace will
read the old/invalid property value/state. So this patch masks away
the WARNING without addressing the actual issue.
Instead can we fix the respective drivers, so that no properties are
created after drm_dev_register()?
Longer version:
As we look into drm_dev_register() it's in charge of creating the
dev/sysfs nodes (et al). Note that connectors cannot disappear at
runtime.
For panel orientation, we are creating an immutable connector
properly, meaning that as soon as drm_dev_register() is called we must
ensure that the property is available (if applicable) and set to the
correct value.
For illustration, consider the following scenario:
- DRM modules are loaded late - are not built-in and not part of
initrd (or there's no initrd)
- kernel boots
- plymouth/similar user-space component kicks in before the
driver/module is loaded
- module gets loaded, drm_dev_register() kicks in populating /dev/dri/card0
- plymouth opens the dev node and reads DRM_MODE_PANEL_ORIENTATION_UNKNOWN
- module updates the orientation property
Thanks
Emil
Powered by blists - more mailing lists