[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160609123110.GB31287@localhost>
Date: Thu, 9 Jun 2016 08:31:10 -0400
From: Bob Copeland <me@...copeland.com>
To: Deepa Dinamani <deepa.kernel@...il.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Arnd Bergmann <arnd@...db.de>,
Thomas Gleixner <tglx@...utronix.de>,
Al Viro <viro@...iv.linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
y2038@...ts.linaro.org, Artem Bityutskiy <dedekind1@...il.com>,
Adrian Hunter <adrian.hunter@...el.com>,
linux-mtd@...ts.infradead.org,
Evgeniy Dushistov <dushistov@...l.ru>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
Jan Kara <jack@...e.com>, linux-ext4@...r.kernel.org,
David Howells <dhowells@...hat.com>,
linux-afs@...ts.infradead.org,
"Tigran A. Aivazian" <tigran@...azian.fsnet.co.uk>,
Theodore Ts'o <tytso@....edu>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Jan Kara <jack@...e.cz>, Jan Harkes <jaharkes@...cmu.edu>,
coda@...cmu.edu, codalist@...a.cs.cmu.edu,
linux-karma-devel@...ts.sourceforge.net,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time()
On Wed, Jun 08, 2016 at 10:04:45PM -0700, Deepa Dinamani wrote:
> CURRENT_TIME_SEC is not y2038 safe. current_fs_time() will
> be transitioned to use 64 bit time along with vfs in a
> separate patch.
> There is no plan to transistion CURRENT_TIME_SEC to use
> y2038 safe time interfaces.
[...]
> Cc: Bob Copeland <me@...copeland.com>
OMFS parts look sane, thanks.
--
Bob Copeland %% http://bobcopeland.com/
Powered by blists - more mailing lists