From: David Sterba <dsterba@suse•cz>
To: Deepa Dinamani <deepa.kernel@gmail•com>
Cc: linux-fsdevel@vger•kernel.org, linux-kernel@vger•kernel.org,
Naoya Horiguchi <n-horiguchi@ah•jp.nec.com>,
Colin Cross <ccross@android•com>, Arnd Bergmann <arnd@arndb•de>,
pvfs2-developers@beowulf-underground•org,
Kees Cook <keescook@chromium•org>,
Matt Fleming <matt@codeblueprint•co.uk>,
"David S. Miller" <davem@davemloft•net>,
Boaz Harrosh <ooo@electrozaur•com>,
Anton Vorontsov <anton@enomsg•org>,
Joel Becker <jlbec@evilplan•org>, Chris Mason <clm@fb•com>,
Josef Bacik <jbacik@fb•com>,
"J. Bruce Fields" <bfields@fieldses•org>,
Eric Van Hensbergen <ericvh@gmail•com>,
Firo Yang <firogm@gmail•com>,
Hal Rosenstock <hal.rosenstock@gmail•com>,
Konstantin Khlebnikov <koct9i@gmail•com>,
Prasad Joshi <prasadjoshi.linux@gmail•com>,
Hugh Dickins <hughd@google•com>,
"Serge E. Hallyn" <serge@hallyn•com>,
Nadia Yvette Chambers <nyc@holomorphy•com>,
Peter Hurley <peter@hurleysof
Subject: Re: [PATCH 04/21] fs: Replace CURRENT_TIME with current_fs_time() for inode timestamps
Date: Thu, 9 Jun 2016 09:55:39 +0200 [thread overview]
Message-ID: <20160609075539.GF3905@suse.cz> (raw)
In-Reply-To: <1465448705-25055-5-git-send-email-deepa.kernel@gmail.com>
On Wed, Jun 08, 2016 at 10:04:48PM -0700, Deepa Dinamani wrote:
> CURRENT_TIME macro is not appropriate for filesystems as it
> doesn't use the right granularity for filesystem timestamps.
> Use current_fs_time() instead.
>
> CURRENT_TIME is also not y2038 safe.
>
> This is also in preparation for the patch that transitions
> vfs timestamps to use 64 bit time and hence make them
> y2038 safe. As part of the effort current_fs_time() will be
> extended to do range checks. Hence, it is necessary for all
> file system timestamps to use current_fs_time(). Also,
> current_fs_time() will be transitioned along with vfs to be
> y2038 safe.
>
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail•com>
> Cc: David Sterba <dsterba@suse•com>
for the btrfs bits
Reviewed-by: David Sterba <dsterba@suse•com>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack•org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack•org"> email@kvack•org </a>
next prev parent reply other threads:[~2016-06-09 7:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 5:04 [PATCH 00/21] Delete CURRENT_TIME and CURRENT_TIME_SEC macros Deepa Dinamani
2016-06-09 5:04 ` [PATCH 04/21] fs: Replace CURRENT_TIME with current_fs_time() for inode timestamps Deepa Dinamani
2016-06-09 7:55 ` David Sterba [this message]
2016-06-09 10:28 ` Steven Whitehouse
2016-06-09 19:08 ` Linus Torvalds
2016-06-09 20:38 ` Deepa Dinamani
2016-06-09 21:02 ` Linus Torvalds
2016-06-10 22:23 ` Arnd Bergmann
[not found] ` <1465448705-25055-1-git-send-email-deepa.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-09 7:51 ` [PATCH 00/21] Delete CURRENT_TIME and CURRENT_TIME_SEC macros Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2016-06-09 13:05 [PATCH 04/21] fs: Replace CURRENT_TIME with current_fs_time() for inode timestamps Ryusuke Konishi
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=20160609075539.GF3905@suse.cz \
--to=dsterba@suse$(echo .)cz \
--cc=anton@enomsg$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=bfields@fieldses$(echo .)org \
--cc=ccross@android$(echo .)com \
--cc=clm@fb$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=deepa.kernel@gmail$(echo .)com \
--cc=ericvh@gmail$(echo .)com \
--cc=firogm@gmail$(echo .)com \
--cc=hal.rosenstock@gmail$(echo .)com \
--cc=hughd@google$(echo .)com \
--cc=jbacik@fb$(echo .)com \
--cc=jlbec@evilplan$(echo .)org \
--cc=keescook@chromium$(echo .)org \
--cc=koct9i@gmail$(echo .)com \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=matt@codeblueprint$(echo .)co.uk \
--cc=n-horiguchi@ah$(echo .)jp.nec.com \
--cc=nyc@holomorphy$(echo .)com \
--cc=ooo@electrozaur$(echo .)com \
--cc=peter@hurleysof \
--cc=prasadjoshi.linux@gmail$(echo .)com \
--cc=pvfs2-developers@beowulf-underground$(echo .)org \
--cc=serge@hallyn$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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