From: Arnd Bergmann <arnd@arndb.de>
To: y2038@lists.linaro.org
Cc: Deepa Dinamani <deepa.kernel@gmail.com>,
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 [thread overview]
Message-ID: <2799630.v7G7zyNKWX@wuerfel> (raw)
In-Reply-To: <1456932710-10926-2-git-send-email-deepa.kernel@gmail.com>
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 <deepa.kernel@gmail.com>
>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2016-03-02 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 15:31 [PATCH 0/2] Add infrastructure to support vfs 64 bit times Deepa Dinamani
2016-03-02 15:31 ` [PATCH 1/2] fs: Add current_fs_time_sec() function Deepa Dinamani
2016-03-02 16:21 ` Arnd Bergmann [this message]
2016-03-02 15:31 ` [PATCH 2/2] vfs: Add vfs_time accessors Deepa Dinamani
2016-03-02 16:21 ` [Y2038] " Arnd Bergmann
2016-03-02 16:22 ` [Y2038] [PATCH 0/2] Add infrastructure to support vfs 64 bit times Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2799630.v7G7zyNKWX@wuerfel \
--to=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox