From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
peter.hutterer@who-t.net, arnd@arndb.de, y2038@lists.linaro.org
Subject: Re: [PATCH v5 1/3] uinput: Use monotonic times for uinput timestamps.
Date: Mon, 1 Jan 2018 22:46:52 -0800 [thread overview]
Message-ID: <20180102064652.jjf4h4m33atgprbb@dtor-ws> (raw)
In-Reply-To: <20171218051844.10193-2-deepa.kernel@gmail.com>
On Sun, Dec 17, 2017 at 09:18:42PM -0800, Deepa Dinamani wrote:
> struct timeval which is part of struct input_event to
> maintain the event times is not y2038 safe.
>
> Real time timestamps are also not ideal for input_event
> as this time can go backwards as noted in the patch
> a80b83b7b8 by John Stultz.
>
> The patch switches the timestamps to use monotonic time
> from realtime time. This is assuming no one is using
> absolute times from these timestamps.
>
> The structure to maintain input events will be changed
> in a different patch.
>
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
> Acked-by: Peter Hutterer <peter.hutterer@who-t.net>
Applied, thank you.
> ---
> drivers/input/misc/uinput.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/misc/uinput.c b/drivers/input/misc/uinput.c
> index 91df0df15e68..9251765645d1 100644
> --- a/drivers/input/misc/uinput.c
> +++ b/drivers/input/misc/uinput.c
> @@ -84,11 +84,14 @@ static int uinput_dev_event(struct input_dev *dev,
> unsigned int type, unsigned int code, int value)
> {
> struct uinput_device *udev = input_get_drvdata(dev);
> + struct timespec64 ts;
>
> udev->buff[udev->head].type = type;
> udev->buff[udev->head].code = code;
> udev->buff[udev->head].value = value;
> - do_gettimeofday(&udev->buff[udev->head].time);
> + ktime_get_ts64(&ts);
> + udev->buff[udev->head].time.tv_sec = ts.tv_sec;
> + udev->buff[udev->head].time.tv_usec = ts.tv_nsec / NSEC_PER_USEC;
> udev->head = (udev->head + 1) % UINPUT_BUFFER_SIZE;
>
> wake_up_interruptible(&udev->waitq);
> --
> 2.14.1
>
--
Dmitry
next prev parent reply other threads:[~2018-01-02 6:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 5:18 [PATCH v5 0/3] Make input drivers y2038 safe Deepa Dinamani
2017-12-18 5:18 ` [PATCH v5 1/3] uinput: Use monotonic times for uinput timestamps Deepa Dinamani
2018-01-02 6:46 ` Dmitry Torokhov [this message]
2017-12-18 5:18 ` [PATCH v5 2/3] input: evdev: Replace timeval with timespec64 Deepa Dinamani
2018-01-02 6:46 ` Dmitry Torokhov
2018-01-02 15:35 ` Arnd Bergmann
2018-01-06 21:43 ` Deepa Dinamani
2018-01-08 20:54 ` Dmitry Torokhov
2017-12-18 5:18 ` [PATCH v5 3/3] input: Deprecate real timestamps beyond year 2106 Deepa Dinamani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180102064652.jjf4h4m33atgprbb@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox