Re: [PATCH 4/5] drm: Check mode object lease status in all master ioctl paths [v3]

On Thu, Oct 12, 2017 at 06:56:30PM -0700, Keith Packard wrote: > Attempts to modify un-leased objects are rejected with an error. > Information returned about unleased objects is modified to make them > appear unusable and/or disconnected. > > Changes for v2 as suggested by Daniel Vetter

Re: [PATCH 4/5] drm: Check mode object lease status in all master ioctl paths [v3]

On Thu, Oct 12, 2017 at 06:56:30PM -0700, Keith Packard wrote: > Attempts to modify un-leased objects are rejected with an error. > Information returned about unleased objects is modified to make them > appear unusable and/or disconnected. > > Changes for v2 as suggested by Daniel Vetter : > >

[PATCH 4/5] drm: Check mode object lease status in all master ioctl paths [v3]

Attempts to modify un-leased objects are rejected with an error. Information returned about unleased objects is modified to make them appear unusable and/or disconnected. Changes for v2 as suggested by Daniel Vetter : * With the change in the __drm_mode_object_find API

[PATCH 4/5] drm: Check mode object lease status in all master ioctl paths [v3]

Attempts to modify un-leased objects are rejected with an error. Information returned about unleased objects is modified to make them appear unusable and/or disconnected. Changes for v2 as suggested by Daniel Vetter : * With the change in the __drm_mode_object_find API to pass the file_priv