Thread (2 messages) 2 messages, 2 authors, 2016-11-15

Re: [RESEND] fs: ext4: Use current_time() for inode timestamps

From: Theodore Ts'o <tytso@mit.edu>
Date: 2016-11-15 02:53:25
Also in: lkml

On Fri, Nov 11, 2016 at 10:32:57AM -0800, Deepa Dinamani wrote:
CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe.
current_time() will be transitioned to be y2038 safe
along with vfs.

current_time() returns timestamps according to the
granularities set in the super_block.
The granularity check in ext4_current_time() to call
current_time() or CURRENT_TIME_SEC is not required.
Use current_time() directly to obtain timestamps
unconditionally, and remove ext4_current_time().

Quota files are assumed to be on the same filesystem.
Hence, use current_time() for these files as well.

Signed-off-by: Deepa Dinamani <redacted>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Thanks, applied.

					- Ted
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help