[PATCH 01/13] drm/amdgpu: introduce and honour DRM_FORCE_AUTH workaround
emil.l.velikov at gmail.com
Thu Jun 20 16:30:12 UTC 2019
On 2019/06/14, Koenig, Christian wrote:
> Am 14.06.19 um 17:53 schrieb Emil Velikov:
> > On 2019/06/14, Koenig, Christian wrote:
> >> Am 14.06.19 um 14:09 schrieb Emil Velikov:
> >>> On 2019/05/27, Emil Velikov wrote:
> >>> [SNIP]
> >>> Hi Christian,
> >>> In the following, I would like to summarise and emphasize the need for
> >>> DRM_AUTH removal. I would kindly ask you to spend a couple of minutes
> >>> extra reading it.
> >>> Today DRM drivers* do not make any distinction between primary and
> >>> render node clients.
> >> That is actually not 100% correct. We have a special case where a DRM
> >> master is allowed to change the priority of render node clients.
> > Can you provide a link? I cannot find that code.
> See amdgpu_sched_ioctl().
> >>> Thus for a render capable driver, any premise of
> >>> separation, security or otherwise imposed via DRM_AUTH is a fallacy.
> >> Yeah, that's what I agree on. I just don't think that removing DRM_AUTH
> >> now is the right direction to take.
> > Could have been clearer - I'm talking about DRM_AUTH | DRM_RENDER_ALLOW
> > ioctls.
> > That aside, can you propose an alternative solution that addresses this
> > and the second point just below?
> Give me a few days to work on this, it's already Friday 6pm here.
Any progress? As mentioned earlier, I'm OK with writing the patches although
I would love to hear your plan.
More information about the amd-gfx