linux-kernel - Re: [PATCH] USB: usbmon: Use 64bit timestamp for mon_bin

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>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 5 May 2015 10:52:33 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Tina Ruchandani <ruchandani.tina@...il.com>
cc:	Oliver Neukum <oneukum@...e.de>, Arnd Bergmann <arnd@...db.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb <linux-usb@...r.kernel.org>,
	Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] USB: usbmon: Use 64bit timestamp for mon_bin_hdr

On Mon, 4 May 2015, Tina Ruchandani wrote:

> > but the timestamp will also overflow. So what is the point?
> >
> 
> The 32-bit timestamp obtained using do_gettimeofday() will overflow in
> year 2038. However, with 64-bit timestamps, we get practically
> infinite time. mon_bin_hdr already has support for a 64-bit seconds
> timestamp. This patch changes how it is populated.

Surely the real point was mentioned in the patch description:

> ... This patch is part of a larger
> attempt to remove instances of struct timeval and other 32-bit timekeeping
> (time_t, struct timespec) from the kernel.

The point is to get rid of 32-bit timekeeping routines.  Overflow and 
the exact nature of the timestamps in usbmon are irrelevant.

Alan Stern

--
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/