On Tue, 25 Jan 2005 15:12:05 -0800, "Micon, David" <[EMAIL PROTECTED]> wrote:
> add_wait_queue(&list->hiddev->wait, &wait);
> - set_current_state(TASK_INTERRUPTIBLE);
>
> while (list->head == list->tail) {
> +
Hi,
A read to an HID device can cause the inner loop in hiddev_read to become a
polling loop instead of blocking. This is because after the first time
through the loop, the task state stays at TASK_RUNNING and the call to
schedule() does not block.
Please incorporate this patch to fix it.
Dave
Hi,
A read to an HID device can cause the inner loop in hiddev_read to become a
polling loop instead of blocking. This is because after the first time
through the loop, the task state stays at TASK_RUNNING and the call to
schedule() does not block.
Please incorporate this patch to fix it.
.
<>
