Re: [PATCH libXrandr 1/2] fix: doGetScreenResources() info: redundant null check on calling free()

2016-08-13 Thread Hans de Goede
Hi, On 12-08-16 18:10, walter harms wrote: Am 12.08.2016 16:36, schrieb Hans de Goede: Hi, On 12-08-16 16:09, walter harms wrote: Am 12.08.2016 12:11, schrieb Hans de Goede: Hi, On 28-07-16 19:31, walter harms wrote: janitorial patch: remove some unneeded if() before free() This is

[PATCH xf86-input-libinput] Bail when a sub-device is it's own parent

2016-08-13 Thread Keith Packard
I don't understand when or how this can happen, but 'make check' in libinput causes this many times: [ 68331.672] (EE) libinput: litest ROCCAT ROCCAT Kone XTD: Parent device is self? [ 68331.996] (EE) libinput: litest Microsoft Surface Type Cover: Parent device is self? [ 68335.260] (EE) libinpu

[PATCH xserver 0/2] os: Handle ospoll callbacks adding/removing fds

2016-08-13 Thread Keith Packard
Here are a couple of patches which deal with the case where the fd callback ends up enabling or disabling file descriptors. ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/l

[PATCH xserver 2/2] os: Abandon loop after poll call when array of fds has changed

2016-08-13 Thread Keith Packard
If a file descriptor is added or removed from an ospoll callback, then the arrays containing file descriptor information will have all of their indices changed, so the loop state is no longer consistent. Just bail out and let the caller come back around to try again. Signed-off-by: Keith Packard

[PATCH xserver 1/2] os: Delay freeing of epoll_wait return pointers until epoll is idle.

2016-08-13 Thread Keith Packard
Instead of freeing the struct ospollfd elements when the fd is removed by the user, delay that until epoll is idle so that we are sure no epoll_event structures could contain the stale pointer. This handles cases where an fd is removed from the ospoll callback interface, and also in case the OS kee

[PATCH xserver] dix: Avoid writing uninitialized bytes in deliverPropertyNotifyEvent

2016-08-13 Thread Keith Packard
Make sure the whole event is initialized, instead of leaving the pad bytes unset. Signed-off-by: Keith Packard --- dix/property.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/dix/property.c b/dix/property.c index bde2af8..fa4da2d 100644 --- a/dix/property.c +++