[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190218142110.GA23087@casa>
Date: Mon, 18 Feb 2019 15:21:10 +0100
From: Rodrigo Rivas Costa <rodrigorivascosta@...il.com>
To: linux-kernel@...r.kernel.org
Cc: dmitry.torokhov@...il.com, rodrigorivascosta@...il.com,
Marcos Paulo de Souza <marcos.souza.org@...il.com>,
Peter Hutterer <peter.hutterer@...-t.net>,
"Paul E. McKenney" <paulmck@...ux.ibm.com>,
Martin Kepplinger <martink@...teo.de>,
"open list:INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN)"
<linux-input@...r.kernel.org>
Subject: Re: [PATCH] Input: uinput - Allow uinput_request to be interrupted
On Sun, Feb 17, 2019 at 09:42:52PM -0300, Marcos Paulo de Souza wrote:
> - if (!wait_for_completion_timeout(&request->done, 30 * HZ)) {
> + if (!wait_for_completion_interruptible_timeout(&request->done,
> + 30 * HZ)) {
> retval = -ETIMEDOUT;
> goto out;
> }
Now this function can succeed or fail because of ETIMEDOUT or an
interrupt. I think you should return -EINTR or maybe -ESYSRESTART if
interrupted.
Powered by blists - more mailing lists