On Sun, Jan 25, 2015 at 12:37:31PM -0500, Rob Clark wrote:
> On Wed, Jan 21, 2015 at 4:40 PM, Rob Clark wrote:
> > On Wed, Jan 21, 2015 at 9:41 AM, Daniel Vetter
> > wrote:
> >> There's a race window (small for hpd, 10s large for polled outputs)
> >> where userspace could sneak in with an unrela
On Wed, Jan 21, 2015 at 4:40 PM, Rob Clark wrote:
> On Wed, Jan 21, 2015 at 9:41 AM, Daniel Vetter
> wrote:
>> There's a race window (small for hpd, 10s large for polled outputs)
>> where userspace could sneak in with an unrelated connnector probe
>> ioctl call and eat the hotplug event (since n
On Wed, Jan 21, 2015 at 9:41 AM, Daniel Vetter
wrote:
> There's a race window (small for hpd, 10s large for polled outputs)
> where userspace could sneak in with an unrelated connnector probe
> ioctl call and eat the hotplug event (since neither the hpd nor the
> poll code see a state change).
>
There's a race window (small for hpd, 10s large for polled outputs)
where userspace could sneak in with an unrelated connnector probe
ioctl call and eat the hotplug event (since neither the hpd nor the
poll code see a state change).
To avoid this, check whether the connector state changes in all o
