From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([217.72.192.73]:64740 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751789AbcDIBQ7 (ORCPT ); Fri, 8 Apr 2016 21:16:59 -0400 From: Arnd Bergmann To: Deepa Dinamani Subject: Re: [PATCH 1/2] fs: Add current_fs_time_sec() function Date: Sat, 9 Apr 2016 03:16:41 +0200 Cc: linux-fsdevel@vger.kernel.org, y2038@lists.linaro.org, tglx@linutronix.de, viro@zeniv.linux.org.uk References: <1460130431-7865-1-git-send-email-deepa.kernel@gmail.com> <1460130431-7865-2-git-send-email-deepa.kernel@gmail.com> In-Reply-To: <1460130431-7865-2-git-send-email-deepa.kernel@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201604090316.41741.arnd@arndb.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Friday 08 April 2016, Deepa Dinamani wrote: > This is in preparation for the series that transitions > filesystem timestamps to use 64 bit time and hence make > them y2038 safe. > > The function is meant to replace CURRENT_TIME_SEC macro. > The macro CURRENT_TIME_SEC does not represent filesystem times > correctly as it cannot perform range checks. > current_fs_time_sec() will be extended to include these. > > CURRENT_TIME_SEC is also not y2038 safe. current_fs_time_sec() > will be transitioned to use 64 bit time along with vfs in a > separate series. > > The function is inline for now to maintain similar performance > to that of the macro. > > The function takes super block as a parameter to allow for > future range checking of filesystem timestamps. > > Signed-off-by: Deepa Dinamani Reviewed-by: Arnd Bergmann