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
| ||
|
Date: Tue, 27 Sep 2016 23:46:49 +0100 From: Al Viro <viro@...IV.linux.org.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Deepa Dinamani <deepa.kernel@...il.com>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>, Thomas Gleixner <tglx@...utronix.de>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Andrew Morton <akpm@...ux-foundation.org>, Theodore Ts'o <tytso@....edu>, y2038@...ts.linaro.org, Felipe Balbi <balbi@...nel.org>, Steven Whitehouse <swhiteho@...hat.com>, Ryusuke KONISHI <konishi.ryusuke@....ntt.co.jp>, David Sterba <dsterba@...e.com>, Jan Kara <jack@...e.cz> Subject: Re: [PATCH v5 0/5] Introduce current_time() api On Wed, Sep 14, 2016 at 09:45:55AM -0700, Linus Torvalds wrote: > On Wed, Sep 14, 2016 at 7:48 AM, Deepa Dinamani <deepa.kernel@...il.com> wrote: > > The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC macros. > > The macros are not y2038 safe. There is no plan to transition them into being > > y2038 safe. > > This version looks ok to me. > > Al, would you be willing to queue this up for 4.9? Applied.
Powered by blists - more mailing lists