linux-kernel - Re: [PATCH 001/001] [Input:] Propagate hardware generated event timestamp to evdev.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 16 Jul 2013 16:22:50 -0700
From:	Michael Wright <michaelwr@...roid.com>
To:	Michael Wright <michaelwr@...roid.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Alexander Levitskiy <sanek@...gle.com>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, Rob Landley <rob@...dley.net>,
	Henrik Rydberg <rydberg@...omail.se>,
	Arve Hjønnevåg <arve@...roid.com>,
	Stephen Boyd <sboyd@...eaurora.org>
Subject: Re: [PATCH 001/001] [Input:] Propagate hardware generated event
 timestamp to evdev.

Apologies, forgot to make sure it was plain text.

On Tue, Jul 16, 2013 at 4:16 PM, Michael Wright <michaelwr@...roid.com> wrote:
> Hi Dmitry,
>
>
> On Fri, Jul 12, 2013 at 11:44 PM, Dmitry Torokhov
> <dmitry.torokhov@...il.com> wrote:
>> We already have MSC_TIMESTAMP (which is in usec), do you really need
>> nsec resolution?
>
> We don't actually need nsec resolution, usec resolution would be sufficient.
>
>
>> Why do you need this special handling? Can you simply have MSC_TIMESTAMP
>> to be delivered as part of the event packet and use it instead of the
>> event timestamp if userspace chooses to do so?
>
> We need stronger guarantees than MSC_TIMESTAMP gives us. Much of
> our system relies on the fact that timestamps produced by evdev are based on
> the systems monotonic clock, whereas MSC_TIMESTAMP provides no such
> guarantee.
> As for whether it's a MSC or SYN event, I don't think we really have
> preference.
>
> Thanks,
>
> Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/