From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.126.131]:58647 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752046AbcCBQVl (ORCPT ); Wed, 2 Mar 2016 11:21:41 -0500 From: Arnd Bergmann To: y2038@lists.linaro.org Cc: Deepa Dinamani , linux-fsdevel@vger.kernel.org, tglx@linutronix.de, viro@zeniv.linux.org.uk Subject: Re: [Y2038] [PATCH 1/2] fs: Add current_fs_time_sec() function Date: Wed, 02 Mar 2016 17:21:28 +0100 Message-ID: <2799630.v7G7zyNKWX@wuerfel> In-Reply-To: <1456932710-10926-2-git-send-email-deepa.kernel@gmail.com> References: <1456932710-10926-1-git-send-email-deepa.kernel@gmail.com> <1456932710-10926-2-git-send-email-deepa.kernel@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wednesday 02 March 2016 07:31:49 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 > Acked-by: Arnd Bergmann