public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: CONFIG_DRM_LEGACY
Date: Sun, 10 Jul 2022 10:00:12 +0000	[thread overview]
Message-ID: <f9e7bc99-bf8b-8a5d-fbfc-01b5d59fdf9d@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

Hello development folks,

recently, it has been flagged to me that we ship our kernels with CONFIG_DRM_LEGACY enabled.

The documentation to this reads:

> Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous
> APIs to user-space, which can be used to circumvent access
> restrictions and other security measures. For backwards compatibility
> those drivers are still available, but their use is highly
> inadvisable and might harm your system.
> 
> You are recommended to use the safe modeset-only drivers instead, and
> perform 3D emulation in user-space.
> 
> Unless you have strong reasons to go rogue, say "N".

Because of the kernel released on July 7 and its fixes to ASIX USB-to-Ethernet adapters, I
am currently working on that sector of IPFire 2.x anyway. Unless somebody of you can recall
why we really need to have CONFIG_DRM_LEGACY enabled, I would submit a patch disabling it -
its documentation does not inspire confidence at all. :-)

Thanks, and best regards,
Peter Müller

             reply	other threads:[~2022-07-10 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10 10:00 Peter Müller [this message]
2022-07-10 11:12 ` CONFIG_DRM_LEGACY Adolf Belka
2022-07-12 10:22   ` CONFIG_DRM_LEGACY Michael Tremer

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=f9e7bc99-bf8b-8a5d-fbfc-01b5d59fdf9d@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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