linux-kernel - Re: [PATCH v3 15/24] drivers: staging: lustre: Replace CURRENT_TIME with current

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: <20160625214514.GA11267@kroah.com>
Date:	Sat, 25 Jun 2016 14:45:14 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Deepa Dinamani <deepa.kernel@...il.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	arnd@...db.de, tglx@...utronix.de, torvalds@...ux-foundation.org,
	tytso@....edu, viro@...iv.linux.org.uk, y2038@...ts.linaro.org,
	lustre-devel@...ts.lustre.org
Subject: Re: [PATCH v3 15/24] drivers: staging: lustre: Replace CURRENT_TIME
 with current_time()

On Sat, Jun 25, 2016 at 02:37:39PM -0700, Deepa Dinamani wrote:
> CURRENT_TIME macro is not appropriate for filesystems as it
> doesn't use the right granularity for filesystem timestamps.
> Use current_time() instead.
> 
> This is also in preparation for the patch that transitions
> vfs timestamps to use 64 bit time and hence make them
> y2038 safe. As part of the effort current_time() will be
> extended to do range checks. Hence, it is necessary for all
> file system timestamps to use current_time().
> 
> Also change format string for prints so that these are valid
> when vfs is transitioned to use 64 bit timestamps.
> 
> Signed-off-by: Deepa Dinamani <deepa.kernel@...il.com>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Cc: lustre-devel@...ts.lustre.org
> Acked-by: James Simmons <jsimmons@...radead.org>

Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>