linux-kernel - Re: [PATCH] net: dns_resolver: convert time_t to time64

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]

Message-ID: <4702816.H75zDcB06x@wuerfel>
Date:	Wed, 18 Nov 2015 22:08:54 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	David Miller <davem@...emloft.net>
Cc:	mahfouz.saif.elyazal@...il.com, dhowells@...hat.com,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] net: dns_resolver: convert time_t to time64_t

On Wednesday 18 November 2015 15:20:25 David Miller wrote:
> From: Aya Mahfouz <mahfouz.saif.elyazal@...il.com>
> Date: Wed, 18 Nov 2015 08:36:44 +0200
> 
> > Changes the definition of the pointer _expiry from time_t to
> > time64_t. This is to handle the Y2038 problem where time_t
> > will overflow in the year 2038. The change is safe because
> > the kernel subsystems that call dns_query pass NULL.
> > 
> > Signed-off-by: Arnd Bergmann <arnd@...db.de>
> > Signed-off-by: Aya Mahfouz <mahfouz.saif.elyazal@...il.com>
> > ---
> > Changelog:
> > v1: The changes were originally made by Arnd Bergmann in
> > relation to time_t. I've broken down a patch sent to me
> > into two independent patches.
> 
> Want me to apply this to 'net'?

Yes, I think that would be good. The original patch was touching
both the key and net subsystems, but this patch makes sense by itself
now, and it helps keep the other half isolated to the key code.

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