Re: [PATCH xf86-input-libinput] Fix crash when using threaded input and the first device goes away

Hi, On 10/10/2016 11:10 AM, Emil Velikov wrote: Hi Hans, On Wednesday, 5 October 2016, Hans de Goede > wrote: When the xserver uses threaded input, it keeps a pointer to the InputInfo passed into xf86AddEnabledDevice and calls

Re: [PATCH xf86-input-libinput] Fix crash when using threaded input and the first device goes away

Hi Hans, On Wednesday, 5 October 2016, Hans de Goede wrote: > When the xserver uses threaded input, it keeps a pointer to the InputInfo > passed into xf86AddEnabledDevice and calls pointer->read_input on events. > > But when the first enabled device goes away the pInfo

Re: [PATCH xf86-input-libinput] Fix crash when using threaded input and the first device goes away

Hi, On 05-10-16 15:31, Hans de Goede wrote: When the xserver uses threaded input, it keeps a pointer to the InputInfo passed into xf86AddEnabledDevice and calls pointer->read_input on events. But when the first enabled device goes away the pInfo we've passed into xf86AddEnabledDevice gets

[PATCH xf86-input-libinput] Fix crash when using threaded input and the first device goes away

When the xserver uses threaded input, it keeps a pointer to the InputInfo passed into xf86AddEnabledDevice and calls pointer->read_input on events. But when the first enabled device goes away the pInfo we've passed into xf86AddEnabledDevice gets freed and eventually pInfo->read_input gets