linux-kernel - Re: [RESEND 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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 5 Nov 2015 08:37:39 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Tina Ruchandani <ruchandani.tina@...il.com>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	y2038 <y2038@...ts.linaro.org>
Subject: Re: [RESEND PATCH] USB: usbmon: Use 64bit timestamp for mon_bin_hdr

On Thu, Nov 05, 2015 at 05:18:41PM +0100, Arnd Bergmann wrote:
> On Thursday 29 October 2015 22:44:31 Tina Ruchandani wrote:
> > struct mon_bin_hdr allows for a 64-bit seconds timestamp. The code
> > currently uses 'struct timeval' to populate the timestamp in mon_bin_hdr,
> > which has a 32-bit seconds field and will overflow in year 2038 and beyond.
> > This patch replaces 'struct timeval' with 'struct timespec64' which is
> > y2038 safe. 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.
> > 
> > Signed-off-by: Tina Ruchandani <ruchandani.tina@...il.com>
> 
> Reviewed-by: Arnd Bergmann <arnd@...db.de>
> 
> As the patch is a week old and Greg hasn't picked it up yet, I'm guessing
> that he doesn't have it in his queue any more and you should send it once
> more with my 'Reviewed-by' tag.

It's the merge window, I can't pick anything new up, please be patient
and wait for 4.4-rc1 to come out first...

thanks,

greg k-h
--
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/