[PATCH 2/3] drm: introduce DRIVER_FORCE_AUTH

Koenig, Christian Christian.Koenig at amd.com
Wed Jul 3 14:58:08 UTC 2019

Am 03.07.2019 16:51 schrieb Emil Velikov <emil.l.velikov at gmail.com>:
On Wed, 3 Jul 2019 at 15:33, Koenig, Christian <Christian.Koenig at amd.com> wrote:
> Am 03.07.2019 16:00 schrieb Emil Velikov <emil.l.velikov at gmail.com>:
> On Wed, 3 Jul 2019 at 14:48, Koenig, Christian <Christian.Koenig at amd.com> wrote:
> >
> > Well this is still a NAK.
> >
> > As stated previously please just don't remove DRM_AUTH and keep the functionality as it is.
> >
> AFAICT nobody was in favour of your suggestion to remove DRM_AUTH from
> the handle to/from fd ioclts.
> Thus this seems like the second best option.
> Well just keep it. As I said please don't change anything here.
> Dropping DRM_AUTH from the driver IOCTLs was sufficient to work around the problems at hand far as I know.
We also need the DRM_AUTH for handle to/from fd ones. Mesa drivers use
those ioctls.

Yeah, but only for importing/exporting things.

And in those cases we either already gave render nodes or correctly authenticated primary nodes.

So no need to change anything here as far as I see.

I simply want to prevent that userspace gets the same functionality from the primary node they get from the render node. And that actually seems to be a good way to keep the restriction and still work around the userspace problems.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20190703/13330064/attachment.html>

More information about the amd-gfx mailing list