From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
Borislav Petkov <bp@suse.de>,
Changcheng Deng <deng.changcheng@zte.com.cn>,
Daniel Vetter <daniel@ffwll.ch>,
Hans de Goede <hdegoede@redhat.com>, Helge Deller <deller@gmx.de>,
Johan Hovold <johan@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Miaoqian Lin <linmq006@gmail.com>,
Peter Jones <pjones@redhat.com>, Sam Ravnborg <sam@ravnborg.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Yizhuo Zhai <yzhai003@ucr.edu>,
Zhen Lei <thunder.leizhen@huawei.com>,
linux-doc@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v3 0/5] Fix some race conditions that exists between fbmem and sysfb
Date: Mon, 25 Apr 2022 10:54:29 +0200 [thread overview]
Message-ID: <535ebbe4-605c-daf5-1afb-f5225e4bb3a8@suse.de> (raw)
In-Reply-To: <20220420085303.100654-1-javierm@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 4794 bytes --]
Hi
Am 20.04.22 um 10:52 schrieb Javier Martinez Canillas:
> Hello,
>
> The patches in this series are mostly changes suggested by Daniel Vetter
> to fix some race conditions that exists between the fbdev core (fbmem)
> and sysfb with regard to device registration and removal.
>
> For example, it is currently possible for sysfb to register a platform
> device after a real DRM driver was registered and requested to remove the
> conflicting framebuffers.
>
> A symptom of this issue, was worked around with by commit fb561bf9abde
> ("fbdev: Prevent probing generic drivers if a FB is already registered")
> but that's really a hack and should be reverted.
As I mentioned on IRC, I think this series should be merged for the
reasons I give in the other comments.
>
> This series attempt to fix it more properly and revert the mentioned hack.
> That will also unblock a pending patch to not make the num_registered_fb
> variable visible to drivers anymore, since that's internal to fbdev core.
Here's as far as I understand the problem:
1) build DRM/fbdev and sysfb code into the kernel
2) during boot, load the DRM/fbdev modules and have them acquire I/O
ranges
3) afterwards load sysfb and have it register platform devices for the
generic framebuffers
4) these devices now conflict with the already-registered DRM/fbdev
devices
If that is the problem here, let's simply set a sysfb_disable flag in
sysfb code when the first DRM/fbdev driver first loads. With the flag
set, sysfb won't create any platform devices. We assume that there are
now DRM/fbdev drivers for the framebuffers and sysfb won't be needed.
We can set the flag internally from drm_aperture_detach_drivers() [1]
and do_remove_conflicting_framebuffers() [2].
Best regards
Thomas
[1]
https://elixir.bootlin.com/linux/v5.17.4/source/drivers/gpu/drm/drm_aperture.c#L253
[2]
https://elixir.bootlin.com/linux/v5.17.4/source/drivers/video/fbdev/core/fbmem.c#L1559
>
> Patch #1 is just a trivial preparatory change.
>
> Patch #2 add sysfb_disable() and sysfb_try_unregister() helpers for fbmem
> to use them.
>
> Patch #3 changes how is dealt with conflicting framebuffers unregistering,
> rather than having a variable to determine if a lock should be take, it
> just drops the lock before unregistering the platform device.
>
> Patch #4 fixes the mentioned race conditions and finally patch #5 is the
> revert patch that was posted by Daniel before but he dropped from his set.
>
> The patches were tested on a rpi4 using different video configurations:
> (simpledrm -> vc4 both builtin, only vc4 builtin, only simpledrm builtin
> and simpledrm builtin with vc4 built as a module).
>
> Best regards,
> Javier
>
> Changes in v3:
> - Rebase on top of latest drm-misc-next branch.
>
> Changes in v2:
> - Rebase on top of latest drm-misc-next and fix conflicts (Daniel Vetter).
> - Add kernel-doc comments and include in other_interfaces.rst (Daniel Vetter).
> - Explain in the commit message that fbmem has to unregister the device
> as fallback if a driver registered the device itself (Daniel Vetter).
> - Also explain that fallback in a comment in the code (Daniel Vetter).
> - Don't encode in fbmem the assumption that sysfb will always register
> platform devices (Daniel Vetter).
> - Add a FIXME comment about drivers registering devices (Daniel Vetter).
> - Drop RFC prefix since patches were already reviewed by Daniel Vetter.
> - Add Daniel Reviewed-by tags to the patches.
>
> Daniel Vetter (1):
> Revert "fbdev: Prevent probing generic drivers if a FB is already
> registered"
>
> Javier Martinez Canillas (4):
> firmware: sysfb: Make sysfb_create_simplefb() return a pdev pointer
> firmware: sysfb: Add helpers to unregister a pdev and disable
> registration
> fbdev: Restart conflicting fb removal loop when unregistering devices
> fbdev: Fix some race conditions between fbmem and sysfb
>
> .../driver-api/firmware/other_interfaces.rst | 6 ++
> drivers/firmware/sysfb.c | 77 +++++++++++++++++--
> drivers/firmware/sysfb_simplefb.c | 16 ++--
> drivers/video/fbdev/core/fbmem.c | 62 ++++++++++++---
> drivers/video/fbdev/efifb.c | 11 ---
> drivers/video/fbdev/simplefb.c | 11 ---
> include/linux/fb.h | 1 -
> include/linux/sysfb.h | 29 +++++--
> 8 files changed, 158 insertions(+), 55 deletions(-)
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-04-25 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 8:52 [PATCH v3 0/5] Fix some race conditions that exists between fbmem and sysfb Javier Martinez Canillas
2022-04-20 8:53 ` [PATCH v3 3/5] fbdev: Restart conflicting fb removal loop when unregistering devices Javier Martinez Canillas
2022-04-25 8:27 ` Thomas Zimmermann
2022-04-25 8:37 ` Javier Martinez Canillas
2022-04-20 8:53 ` [PATCH v3 4/5] fbdev: Fix some race conditions between fbmem and sysfb Javier Martinez Canillas
2022-04-25 8:30 ` Thomas Zimmermann
2022-04-22 15:17 ` [PATCH v3 0/5] Fix some race conditions that exists " Greg Kroah-Hartman
2022-04-25 8:54 ` Thomas Zimmermann [this message]
2022-04-25 9:15 ` Thomas Zimmermann
2022-04-25 9:49 ` Javier Martinez Canillas
2022-04-29 7:47 ` Daniel Vetter
2022-04-29 8:06 ` Javier Martinez Canillas
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=535ebbe4-605c-daf5-1afb-f5225e4bb3a8@suse.de \
--to=tzimmermann@suse.de \
--cc=alexander.deucher@amd.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=deng.changcheng@zte.com.cn \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=javierm@redhat.com \
--cc=johan@kernel.org \
--cc=linmq006@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pjones@redhat.com \
--cc=sam@ravnborg.org \
--cc=thunder.leizhen@huawei.com \
--cc=yzhai003@ucr.edu \
/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;
as well as URLs for NNTP newsgroup(s).