[lkml]   [2018]   [Jan]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v6 0/4]
The series is aimed at adding support to maintain individual
timestamp ranges for filesystems. This helps futimens, utimensat
and utimes syscalls to conform to POSIX defined behavior when
the time being set is outside of the corresponding filesystem's
supported limits.

The series was developed with discussions and guidance from
Arnd Bergmann.

The original thread is at

I will be submitting follow up kernel patches to update all
Currently ext4 is the only filesystem that reflects correct limits.

The branch is available at refs/heads/range

Changes since v5:
* Dropped y2038-specific changes
Changes since v4:
* Added documentation for boot param
Changes since v3:
* Remove redundant initializations in libfs.c
* Change early_param to __setup similar to other root mount options.
* Fix documentation warning
Changes since v2:
* Introduce early boot param override for checks.
* Drop afs patch for timestamp limits.
Changes since v1:
* return EROFS on mount errors
* fix mtime copy/paste error in utimes

Deepa Dinamani (4):
vfs: Add file timestamp range support
ext4: Initialize timestamps limits
vfs: Add timestamp_truncate() api
utimes: Clamp the timestamps before update

fs/ext4/ext4.h | 4 ++++
fs/ext4/super.c | 7 ++++++-
fs/inode.c | 32 +++++++++++++++++++++++++++++++-
fs/super.c | 2 ++
fs/utimes.c | 17 +++++++++++++----
include/linux/fs.h | 3 +++
include/linux/time64.h | 2 ++
7 files changed, 61 insertions(+), 6 deletions(-)


Cc: "Theodore Ts'o" <>
Cc: Andreas Dilger <>

 \ /
  Last update: 2018-01-22 03:07    [W:0.051 / U:2.792 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site