Bug 1212947 - Disable fbdev userspace interfaces and programs
Summary: Disable fbdev userspace interfaces and programs
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Thomas Zimmermann
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on: 1212948 1224053
Blocks:
  Show dependency treegraph
 
Reported: 2023-07-03 12:09 UTC by Thomas Zimmermann
Modified: 2024-05-14 07:12 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Zimmermann 2023-07-03 12:09:20 UTC
We want to remove fbdev from kernel and userspace as far as possible. Linux 6.6 will allow us to disable fbdev's userspace interfaces, most noteably /dev/fb*. Enable this feature in the TW kernel.

Framebuffer support has been an endless source of bugs. Not giving userspace access to it's internals and framebuffer memory will close a possible entry point for all sorts of malware.

Please note that the framebuffer console is implemented entirely within the kernel and will not be affected by this change.
Comment 1 Simon Lees 2023-11-02 06:51:32 UTC
AS mentioned on the mailing list, I have SPI based display's for the Raspberry PI that I still use /dev/fb* with which I think is not uncommon for that platform. There are still tools like fbi and some graphical toolkits that can render directly to the framebuffer that often make sense in that environment.
Comment 2 Michal Suchanek 2023-11-14 10:11:06 UTC
(In reply to Simon Lees from comment #1)
> AS mentioned on the mailing list, I have SPI based display's for the
> Raspberry PI that I still use /dev/fb* with which I think is not uncommon
> for that platform. There are still tools like fbi and some graphical
> toolkits that can render directly to the framebuffer that often make sense
> in that environment.

Any reason why you cannot use DRM for these?
Comment 3 Michal Suchanek 2023-11-14 10:13:54 UTC
Note that /dev/fb* supports /sys/class/graphics/fb0/rotate, not aware of anything like that for DRM.

That means that switching from FB to DRM interface is a regression for people using the kernel interface to tell the application how to rotate the output.

Because the kernel interface exists many applications do not have corresponding userspace option at all.