Commit d13cb974 authored by Peter Hutterer's avatar Peter Hutterer

ddx: add new call to purge input devices that weren't added

Special case for the systemd-logind case in xfree86: when we're vt-switched
away and a device is plugged in, we get a paused fd from logind. Since we
can't probe the device or do anything with it, we store that device in the
xfree86 and handle it later when we vt-switch back. The device is not added to
inputInfo.devices until that time.

When the device is removed while still vt-switched away, the the config system
never notifies the DDX. It only runs through inputInfo.devices and our device
was never added to that.

When a device is plugged in, removed, and plugged in again while vt-switched
away, we have two entries in the xfree86-specific list that refer to the same
device node, both pending for addition later. On VT switch back, the first one
(the already removed one) will be added successfully, the second one (the
still plugged-in one) fails. Since the fd is correct, the device works until
it is removed again. The removed devices' config_info (i.e. the syspath)
doesn't match the actual device we addded tough (the input number increases
with each plug), it doesn't get removed, the fd remains open and we lose track
of the fd count. Plugging the device in again leads to a dead device.

Fix this by adding a call to notify the DDX to purge any remainders of devices
with the given config_info, that's the only identifiable bit we have at this
point.

https://bugs.freedesktop.org/show_bug.cgi?id=97928Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
parent 8fcf2fa7
......@@ -143,3 +143,17 @@ DeleteInputDeviceRequest(DeviceIntPtr dev)
{
RemoveDevice(dev, TRUE);
}
/****************************************************************************
*
* Caller: configRemoveDevice (and others)
*
* Remove any traces of the input device specified in config_info.
* This is only necessary if the ddx keeps information around beyond
* the NewInputDeviceRequest/DeleteInputDeviceRequest
*
*/
void
RemoveInputDeviceTraces(const char *config_info)
{
}
......@@ -107,6 +107,8 @@ remove_devices(const char *backend, const char *config_info)
if (dev->config_info && strcmp(dev->config_info, config_info) == 0)
remove_device(backend, dev);
}
RemoveInputDeviceTraces(config_info);
}
BOOL
......
......@@ -123,3 +123,8 @@ void
DeleteInputDeviceRequest(DeviceIntPtr pDev)
{
}
void
RemoveInputDeviceTraces(const char *config_info)
{
}
......@@ -2302,3 +2302,8 @@ DeleteInputDeviceRequest(DeviceIntPtr pDev)
{
RemoveDevice(pDev, TRUE);
}
void
RemoveInputDeviceTraces(const char *config_info)
{
}
......@@ -1119,6 +1119,21 @@ DeleteInputDeviceRequest(DeviceIntPtr pDev)
input_unlock();
}
void
RemoveInputDeviceTraces(const char *config_info)
{
PausedInputDevicePtr d, tmp;
xorg_list_for_each_entry_safe(d, tmp, &new_input_devices_list, node) {
const char *ci = xf86findOptionValue(d->pInfo->options, "config_info");
if (!ci || strcmp(ci, config_info) != 0)
continue;
xorg_list_del(&d->node);
free(d);
}
}
/*
* convenient functions to post events
*/
......
......@@ -147,3 +147,18 @@ DeleteInputDeviceRequest(DeviceIntPtr dev)
{
DEBUG_LOG("DeleteInputDeviceRequest(%p)\n", dev);
}
/****************************************************************************
*
* Caller: configRemoveDevice (and others)
*
* Remove any traces of the input device specified in config_info.
* This is only necessary if the ddx keeps information around beyond
* the NewInputDeviceRequest/DeleteInputDeviceRequest
*
*/
void
RemoveInputDeviceTraces(const char *config_info)
{
DEBUG_LOG("RemoveInputDeviceTraces(%s)\n", config_info);
}
......@@ -635,6 +635,7 @@ extern _X_EXPORT int NewInputDeviceRequest(InputOption *options,
InputAttributes * attrs,
DeviceIntPtr *dev);
extern _X_EXPORT void DeleteInputDeviceRequest(DeviceIntPtr dev);
extern _X_EXPORT void RemoveInputDeviceTraces(const char *config_info);
extern _X_EXPORT void DDXRingBell(int volume, int pitch, int duration);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment