From: Bob Copeland Subject: Re: [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time() Date: Thu, 9 Jun 2016 08:31:10 -0400 Message-ID: <20160609123110.GB31287@localhost> References: <1465448705-25055-1-git-send-email-deepa.kernel@gmail.com> <1465448705-25055-2-git-send-email-deepa.kernel@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Arnd Bergmann , Thomas Gleixner , Al Viro , Linus Torvalds , y2038@lists.linaro.org, Artem Bityutskiy , Adrian Hunter , linux-mtd@lists.infradead.org, Evgeniy Dushistov , OGAWA Hirofumi , Jan Kara , linux-ext4@vger.kernel.org, David Howells , linux-afs@lists.infradead.org, "Tigran A. Aivazian" , Theodore Ts'o , Andreas Dilger , Jan Kara , Jan Harkes , coda@cs.cmu.edu, codalist@coda.cs.cmu.edu, linux-karma-devel@lists.sourceforge.net, Christoph Hellwig To: Deepa Dinamani Return-path: Content-Disposition: inline In-Reply-To: <1465448705-25055-2-git-send-email-deepa.kernel@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org 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 OMFS parts look sane, thanks. -- Bob Copeland %% http://bobcopeland.com/