struct timeval is not y2038 safe.
All references to timeval in the kernel will be replaced
by y2038 safe structures.
Replace all references to timeval with y2038 safe
struct timespec64 here.
struct input_event will be changed in a different patch.
Signed-off-by: Deepa Dinamani
---
drivers
raw_input_event.The changes to the popular libraries will be
posted along with the kernel changes.
The driver version is also updated to reflect the change in
event format.
Suggested-by: Arnd Bergmann
Signed-off-by: Deepa Dinamani
---
drivers/input/evdev.c| 20 ++--
drivers
Thank you for the suggestion.
> Who are you execting to pull this huge patch series?
The last pull request was addressed to Al as per Arnd's suggestion.
I'm not completely sure who should it be addressed to.
> Why not just introduce the new api call, wait for that to be merged, and
> then push t
s.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
---
fs/inode.c | 23 +++
include/linux/fs.h | 1 +
2 files changed, 24 insertions(+)
diff --git a/fs/inode.c b/fs/inode.c
index fd604c0..a95e04e 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -2075,3 +2075,
ffort current_time() will be
extended to do range checks. Hence, it is necessary for all
file system timestamps to use current_time().
Also change format string for prints so that these are valid
when vfs is transitioned to use 64 bit timestamps.
Signed-off-by: Deepa Dinamani
Acked-by: James Si
used
to change timestamps in different inodes, it is because they
share the same time granularity.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Acked-by: Felipe Balbi
Acked-by: Steven Whitehouse
Acked-by: Ryusuke Konishi
Acked-by: David Sterba
---
arch/powerpc/platforms/cell/
All uses of the current_fs_time() function have been
replaced by other time interfaces.
And, its use cases can be fulfilled by current_time()
or ktime_get_* variants.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: John Stultz
Cc: Thomas Gleixner
---
include/linux/fs.h | 1
range checking is introduced.
This works because alloc_super() fills in the the s_time_gran
in super block to NSEC_PER_SEC.
Signed-off-by: Deepa Dinamani
Acked-by: Jan Kara
---
fs/affs/amigaffs.c | 6 +++---
fs/affs/inode.c | 2 +-
fs/bfs/dir.c| 14 +++---
fs
macro will be deleted before merging the
aforementioned change.
Change signature of helper cifs_all_info_to_fattr since it
now needs both super_block and cifs_sb_info.
Note: The inode timestamps read from the server are assumed
to have correct granularity and range.
Signed-off-by: Deepa Dinamani
Rev
1024 characters.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Acked-by: Paul Moore
Acked-by: Richard Guy Briggs
Cc: Eric Paris
Cc: Paul Moore
Cc: Richard Guy Briggs
Cc: linux-au...@redhat.com
---
include/linux/audit.h | 4 ++--
kernel/audit.c| 10 +-
kernel
) was used to
assign times in proc_alloc_inode().
Signed-off-by: Deepa Dinamani
Reported-by: Fengguang Wu [0-day test robot]
Reviewed-by: Arnd Bergmann
---
fs/proc/inode.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/proc/inode.c b/fs/proc/inode.c
index c1b7238..ce1f1a9 100644
--- a/fs
All uses of CURRENT_TIME_SEC and CURRENT_TIME macros have
been replaced by other time functions. These macros are
also not y2038 safe.
And, all their use cases can be fulfilled by y2038 safe
ktime_get_* variants.
Signed-off-by: Deepa Dinamani
Acked-by: John Stultz
Reviewed-by: Arnd Bergmann
Cc
CURRENT_TIME_SEC is not required.
Use current_time() directly to obtain timestamps
unconditionally, and remove ext4_current_time().
Quota files are assumed to be on the same filesystem.
Hence, use current_time() for these files as well.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: "The
CURRENT_TIME_SEC is not y2038 safe.
Replace use of CURRENT_TIME_SEC with ktime_get_real_seconds
in segment timestamps used by GC algorithm including the
segment mtime timestamps.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: Jaegeuk Kim
Cc: Changman Lee
Cc: linux-f2fs-de
of real time as only delta scan times are
relevant and these values are not persistent across
reboots.
The format string for the debug print is still using long
as this is only the time elapsed since the last scan and
long is sufficient to represent this value.
Signed-off-by: Deepa Dinamani
also wide enough to accommodate time64_t.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: Mark Fasheh
Cc: Joel Becker
Cc: ocfs2-de...@oss.oracle.com
---
fs/ocfs2/cluster/heartbeat.c | 2 +-
fs/ocfs2/inode.c | 2 +-
fs/ocfs2/namei.c | 6 --
3 files chang
timespec64 as well.
Signed-off-by: Deepa Dinamani
Acked-by: David Sterba
Reviewed-by: Arnd Bergmann
Cc: Chris Mason
Cc: David Sterba
Cc: Josef Bacik
Cc: linux-bt...@vger.kernel.org
---
fs/btrfs/root-tree.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/btrfs/root-tree.c
() to truncate the timestamp, using the right
granularity from the superblock.
This api will be transitioned to be y2038 safe along
with vfs.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: "Yan, Zheng"
Cc: Sage Weil
Cc: Ilya Dryomov
Cc: ceph-de...@vger.kernel.org
--
and hence make them
y2038 safe. As part of the effort current_time() will be
extended to do range checks.
Signed-off-by: Deepa Dinamani
Cc: Jan Kara
Reviewed-by: Jan Kara
Reviewed-by: Arnd Bergmann
---
fs/udf/super.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a
x27;s super_block.
The granularity check to call current_fs_time() or
CURRENT_TIME_SEC is not required.
Use current_time() directly to update inode timestamp.
Use timespec_trunc during file system creation, before
the first inode is created.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergman
CURRENT_TIME is not y2038 safe.
Replace it with ktime_get_real_ts64().
Inode time formats are already 64 bit long and
accommodates time64_t.
Signed-off-by: Deepa Dinamani
Cc: Evgeniy Dushistov
---
fs/ufs/ialloc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/ufs
struct timespec64
in a separate patch.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: Ilya Dryomov
Cc: Sage Weil
Cc: Alex Elder
Cc: ceph-de...@vger.kernel.org
---
drivers/block/rbd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/rbd.c b/drivers
between server
and client, and the largest timezone difference is in the
range of one day.
All cifs timestamps currently use timespec internally.
This timestamp can also be transitioned into using
timespec64 when all other timestamps for cifs is transitioned
to use timespec64.
Signed-off-by: Deepa
jfs uses nanosecond granularity for filesystem timestamps.
Only this assignment is not using nanosecond granularity.
Use current_time() to get the right granularity.
Signed-off-by: Deepa Dinamani
Cc: Dave Kleikamp
Acked-by: Dave Kleikamp
Reviewed-by: Arnd Bergmann
Cc: jfs-discuss
part of ktime_t for the authsys_parms
stamp field.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: Trond Myklebust
Cc: Anna Schumaker
Cc: linux-...@vger.kernel.org
---
fs/nfs/client.c | 2 +-
fs/nfs/netns.h| 2 +-
fs/nfs/nfs4proc.c | 10 ++
fs/nfs/nfs4xdr.c | 2
l calls to current_fs_time() to use the new
current_time() function instead. current_fs_time() will be
deleted.
Signed-off-by: Deepa Dinamani
---
drivers/char/sonypi.c | 2 +-
drivers/platform/x86/sony-laptop.c | 2 +-
fs/attr.c | 2 +-
fs/b
struct timespec64
in a separate patch.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: "Yan, Zheng"
Cc: Sage Weil
Cc: Ilya Dryomov
Cc: ceph-de...@vger.kernel.org
---
net/ceph/messenger.c | 6 --
net/ceph/osd_client.c | 4 ++--
2 files changed, 6 insertions(+), 4
trace timestamps use struct timespec and CURRENT_TIME which
are not y2038 safe.
These timestamps are only part of the trace log on the machine
and are not shared with the fnic.
Replace then with y2038 safe struct timespec64 and
ktime_get_real_ts64(), respectively.
Signed-off-by: Deepa Dinamani
timestamps for cifs is transitioned
to use timespec64.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: Steve French
---
fs/cifs/cifsencrypt.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/cifs/cifsencrypt.c b/fs/cifs/cifsencrypt.c
index 8347c90..fd01bf0 100644
08-13 13:44:41 -0700)
----
Deepa Dinamani (26):
vfs: Add current_time() api
fs: proc: Delete inode time initializations in proc_alloc_inode()
fs: Replace CURRENT_TIME with current_time() for inode timestamps
fs: Replace CURRENT_TIME_SEC with current_time() for inode time
current_time-v4.7-rc5
for you to fetch changes up to 1025409988864abcad2670461cf8d5a0fa08d317:
time: Delete CURRENT_TIME_SEC (2016-06-30 18:27:56 -0700)
Deepa Dinamani (24):
vfs: Add current_time() api
fs: proc: Delete inode
used
to change timestamps in different inodes, it is because they
share the same time granularity.
Signed-off-by: Deepa Dinamani
Acked-by: Felipe Balbi
Acked-by: Steven Whitehouse
Acked-by: Ryusuke Konishi
Acked-by: David Sterba
---
arch/powerpc/platforms/cell/spufs/inode.c | 2 +-
arch
ized sb in inode.
* Minor fixes according to Arnd's comments.
* Leave out the fnic and deletion of CURRENT_TIME to be submitted after 4.8 rc1.
Deepa Dinamani (24):
vfs: Add current_time() api
fs: proc: Delete inode time initializations in proc_alloc_inode()
fs: Replace CURRENT_TIME with cur
range checking is introduced.
This works because alloc_super() fills in the the s_time_gran
in super block to NSEC_PER_SEC.
Also note that filesystem specific times like the birthtime,
creation time that were using same interfaces to obtain time
retain same logistics.
Signed-off-by: Deepa
s.
Signed-off-by: Deepa Dinamani
---
fs/inode.c | 23 +++
include/linux/fs.h | 1 +
2 files changed, 24 insertions(+)
diff --git a/fs/inode.c b/fs/inode.c
index e171f7b..80b6898 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -2043,3 +2043,26 @@ void inode_nohighmem(st
l calls to current_fs_time() to use the new
current_time() function instead. current_fs_time() will be
deleted.
Signed-off-by: Deepa Dinamani
---
drivers/char/sonypi.c | 2 +-
drivers/platform/x86/sony-laptop.c | 2 +-
fs/attr.c | 2 +-
fs/b
CURRENT_TIME_SEC is not required.
Use current_time() directly to obtain timestamps
unconditionally, and remove ext4_current_time().
Quota files are assumed to be on the same filesystem.
Hence, use current_time() for these files as well.
Signed-off-by: Deepa Dinamani
Cc: "Theodore Ts'o"
Cc: And
timestamps for cifs is transitioned
to use timespec64.
Signed-off-by: Deepa Dinamani
Cc: Steve French
---
fs/cifs/cifsencrypt.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/cifs/cifsencrypt.c b/fs/cifs/cifsencrypt.c
index 6aeb8d4..b86ce67 100644
--- a/fs/cifs/cifsencrypt.c
macro will be deleted before merging the
aforementioned change.
Change signature of helper cifs_all_info_to_fattr since it
now needs both super_block and cifs_sb_info.
Note: The inode timestamps read from the server are assumed
to have correct granularity and range.
Signed-off-by: Deepa Dinaman
jfs uses nanosecond granularity for filesystem timestamps.
Only this assignment is not using nanosecond granularity.
Use current_time() to get the right granularity.
Signed-off-by: Deepa Dinamani
Cc: Dave Kleikamp
Cc: jfs-discuss...@lists.sourceforge.net
Acked-by: Dave Kleikamp
---
fs/jfs
and hence make them
y2038 safe. As part of the effort current_time() will be
extended to do range checks.
Signed-off-by: Deepa Dinamani
Cc: Jan Kara
Reviewed-by: Jan Kara
---
fs/udf/super.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/fs/udf/super.c b/fs/udf/s
between server
and client, and the largest timezone difference is in the
range of one day.
All cifs timestamps currently use timespec internally.
This timestamp can also be transitioned into using
timespec64 when all other timestamps for cifs is transitioned
to use timespec64.
Signed-off-by: Deepa
timespec64 as well.
Signed-off-by: Deepa Dinamani
Cc: Chris Mason
Cc: Josef Bacik
Cc: David Sterba
Cc: linux-bt...@vger.kernel.org
Acked-by: David Sterba
---
fs/btrfs/root-tree.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/btrfs/root-tree.c b/fs/btrfs/root-tree.c
CURRENT_TIME_SEC is not y2038 safe.
Replace use of CURRENT_TIME_SEC with ktime_get_real_seconds
in segment timestamps used by GC algorithm including the
segment mtime timestamps.
Signed-off-by: Deepa Dinamani
Cc: Jaegeuk Kim
Cc: Changman Lee
Cc: linux-f2fs-de...@lists.sourceforge.net
---
fs
All uses of the current_fs_time() function have been
replaced by other time interfaces.
And, its use cases can be fulfilled by current_time()
or ktime_get_* variants.
Signed-off-by: Deepa Dinamani
Cc: John Stultz
Cc: Thomas Gleixner
---
include/linux/fs.h | 1 -
kernel/time/time.c | 14
x27;s super_block.
The granularity check to call current_fs_time() or
CURRENT_TIME_SEC is not required.
Use current_time() directly to update inode timestamp.
Use timespec_trunc during file system creation, before
the first inode is created.
Signed-off-by: Deepa Dinamani
Cc: Artem Bityutskiy
Cc: A
of real time as only delta scan times are
relevant and these values are not persistent across
reboots.
The format string for the debug print is still using long
as this is only the time elapsed since the last scan and
long is sufficient to represent this value.
Signed-off-by: Deepa Dinamani
Cc
CURRENT_TIME is not y2038 safe.
Use y2038 safe ktime_get_real_seconds() here for timestamps.
struct heartbeat_block's hb_seq and deletetion time are already
64 bits wide and accommodate times beyond y2038.
Signed-off-by: Deepa Dinamani
Cc: Mark Fasheh
Cc: Joel Becker
Cc: ocf
() to truncate the timestamp, using the right
granularity from the superblock.
This api will be transitioned to be y2038 safe along
with vfs.
Signed-off-by: Deepa Dinamani
Cc: "Yan, Zheng"
Cc: Sage Weil
Cc: Ilya Dryomov
Cc: ceph-de...@vger.kernel.org
---
fs/ceph/mds_client.c | 4 ++
struct timespec64
in a separate patch.
Signed-off-by: Deepa Dinamani
Cc: "Yan, Zheng"
Cc: Sage Weil
Cc: Ilya Dryomov
Cc: ceph-de...@vger.kernel.org
---
net/ceph/messenger.c | 6 --
net/ceph/osd_client.c | 4 ++--
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git
All uses of CURRENT_TIME_SEC macro have been replaced by
other time functions. This macro is also not y2038 safe.
And, all its use cases can be fulfilled by y2038 safe
ktime_get_* variants.
Signed-off-by: Deepa Dinamani
Cc: John Stultz
Cc: Thomas Gleixner
Acked-by: John Stultz
---
include
1024 characters.
Signed-off-by: Deepa Dinamani
Cc: Paul Moore
Cc: Eric Paris
Cc: linux-au...@redhat.com
Acked-by: Paul Moore
Acked-by: Richard Guy Briggs
---
include/linux/audit.h | 4 ++--
kernel/audit.c| 10 +-
kernel/audit.h| 2 +-
kernel/auditsc.c | 6
part of ktime_t for the authsys_parms
stamp field.
Signed-off-by: Deepa Dinamani
Cc: Trond Myklebust
Cc: Anna Schumaker
Cc: linux-...@vger.kernel.org
---
fs/nfs/client.c | 2 +-
fs/nfs/netns.h| 2 +-
fs/nfs/nfs4proc.c | 10 ++
fs/nfs/nfs4xdr.c | 2 +-
4 files changed, 9 inser
ffort current_time() will be
extended to do range checks. Hence, it is necessary for all
file system timestamps to use current_time().
Also change format string for prints so that these are valid
when vfs is transitioned to use 64 bit timestamps.
Signed-off-by: Deepa Dinamani
Cc: Greg Kroah-Hartma
struct timespec64
in a separate patch.
Signed-off-by: Deepa Dinamani
Cc: Ilya Dryomov
Cc: Sage Weil
Cc: Alex Elder
Cc: ceph-de...@vger.kernel.org
---
drivers/block/rbd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
index 4506620
) was used to
assign times in proc_alloc_inode().
Signed-off-by: Deepa Dinamani
Reported-by: Fengguang Wu [0-day test robot]
---
fs/proc/inode.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/proc/inode.c b/fs/proc/inode.c
index 6b1843e..606e4cd 100644
--- a/fs/proc/inode.c
+++ b/fs/proc/in
>> @@ -3727,6 +3727,7 @@ static int ext4_cross_rename(struct inode *old_dir,
>> struct dentry *old_dentry,
>> };
>> u8 new_file_type;
>> int retval;
>> + struct timespec ctime;
>>
>> if ((ext4_encrypted_inode(old_dir) ||
>> ext4_encrypted_inode(ne
>> @@ -84,6 +84,8 @@ static int create_default_filesystem(struct ubifs_info *c)
>> int min_leb_cnt = UBIFS_MIN_LEB_CNT;
>> long long tmp64, main_bytes;
>> __le64 tmp_le64;
>> + __le32 tmp_le32;
>> + struct timespec ts;
>>
>> /* Some functions called from
On Wed, Jun 22, 2016 at 6:54 AM, Arnd Bergmann wrote:
> On Sunday, June 19, 2016 5:27:08 PM CEST Deepa Dinamani wrote:
>> mutex_lock(&sbi->s_alloc_mutex);
>> lvidiu->impIdent.identSuffix[0] = UDF_OS_CLASS_UNIX;
>> lvidiu->impIden
On Wed, Jun 22, 2016 at 7:09 AM, Arnd Bergmann wrote:
> On Sunday, June 19, 2016 5:27:18 PM CEST Deepa Dinamani wrote:
>> trace timestamps use struct timespec and CURRENT_TIME which
>> are not y2038 safe.
>> These timestamps are only part of the trace log on the machine
>&
> This version now looks ok to me.
>
> I do have a comment (or maybe just a RFD) for future work.
>
> It does strike me that once we actually change over the inode times to
> use timespec64, the calling conventions are going to be fairly
> horrendous on most 32-bit architectures.
>
> Gcc handles 8-
struct timespec64
in a separate patch.
Signed-off-by: Deepa Dinamani
Cc: Ilya Dryomov
Cc: Sage Weil
Cc: Alex Elder
Cc: ceph-de...@vger.kernel.org
---
drivers/block/rbd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
index 4506620
of real time as only delta scan times are
relevant and these values are not persistent across
reboots.
The format string for the debug print is still using long
as this is only the time elapsed since the last scan and
long is sufficient to represent this value.
Signed-off-by: Deepa Dinamani
Cc
ffort current_time() will be
extended to do range checks. Hence, it is necessary for all
file system timestamps to use current_time().
Also change format string for prints so that these are valid
when vfs is transitioned to use 64 bit timestamps.
Signed-off-by: Deepa Dinamani
Cc: Greg Kroah-Hartma
between server
and client, and the largest timezone difference is in the
range of one day.
All cifs timestamps currently use timespec internally.
This timestamp can also be transitioned into using
timespec64 when all other timestamps for cifs is transitioned
to use timespec64.
Signed-off-by: Deepa
struct timespec64
in a separate patch.
Signed-off-by: Deepa Dinamani
Cc: "Yan, Zheng"
Cc: Sage Weil
Cc: Ilya Dryomov
Cc: ceph-de...@vger.kernel.org
---
net/ceph/messenger.c | 6 --
net/ceph/osd_client.c | 4 ++--
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git
time64_to_tm() is already part of John's
kernel tree: https://lkml.org/lkml/2016/6/17/875 .
Signed-off-by: Deepa Dinamani
Cc: Hiral Patel
Cc: Suma Ramars
Cc: Brian Uchino
Cc: "James E.J. Bottomley"
Cc: "Martin K. Petersen"
Cc: John Stultz
Cc: linux-s...@vger.kernel.o
CURRENT_TIME_SEC is not y2038 safe.
Replace use of CURRENT_TIME_SEC with ktime_get_real_seconds
in segment timestamps used by GC algorithm including the
segment mtime timestamps.
Signed-off-by: Deepa Dinamani
Cc: Jaegeuk Kim
Cc: Changman Lee
Cc: linux-f2fs-de...@lists.sourceforge.net
---
fs
part of ktime_t for the authsys_parms
stamp field.
Signed-off-by: Deepa Dinamani
Cc: Trond Myklebust
Cc: Anna Schumaker
Cc: linux-...@vger.kernel.org
---
Changes from V1:
* Use ktime_t instead of timespec64_t
* Change algorithm to use boot_time accordingly
fs/nfs/client.c | 2 +-
fs/nfs/ne
CURRENT_TIME is not y2038 safe.
Use y2038 safe ktime_get_real_seconds() here for timestamps.
struct heartbeat_block's hb_seq and deletetion time are already
64 bits wide and accommodate times beyond y2038.
Signed-off-by: Deepa Dinamani
Cc: Mark Fasheh
Cc: Joel Becker
Cc: ocf
() to truncate the timestamp, using the right
granularity from the superblock.
This api will be transitioned to be y2038 safe along
with vfs.
Signed-off-by: Deepa Dinamani
Cc: "Yan, Zheng"
Cc: Sage Weil
Cc: Ilya Dryomov
Cc: ceph-de...@vger.kernel.org
---
fs/ceph/mds_client.c | 4 ++
1024 characters.
Signed-off-by: Deepa Dinamani
Cc: Paul Moore
Cc: Eric Paris
Cc: linux-au...@redhat.com
Acked-by: Paul Moore
---
include/linux/audit.h | 4 ++--
kernel/audit.c| 10 +-
kernel/audit.h| 2 +-
kernel/auditsc.c | 6 +++---
4 files changed, 11
All uses of the current_fs_time() function have been
replaced by other time interfaces.
And, its use cases can be fulfilled by current_time()
or ktime_get_* variants.
Signed-off-by: Deepa Dinamani
Cc: John Stultz
Cc: Thomas Gleixner
---
include/linux/fs.h | 1 -
kernel/time/time.c | 14
l calls to current_fs_time() to use the new
current_time() function instead. current_fs_time() will be
deleted.
Signed-off-by: Deepa Dinamani
---
drivers/char/sonypi.c | 2 +-
drivers/platform/x86/sony-laptop.c | 2 +-
fs/attr.c | 2 +-
fs/b
used
to change timestamps in different inodes, it is because they
share the same time granularity.
Signed-off-by: Deepa Dinamani
Acked-by: Felipe Balbi
Acked-by: Steven Whitehouse
Acked-by: Ryusuke Konishi
Reviewed-by: David Sterba
---
arch/powerpc/platforms/cell/spufs/inode.c | 2 +-
arch
jfs uses nanosecond granularity for filesystem timestamps.
Only this assignemt is not using nanosecond granularity.
Use current_time() to get the right granularity.
Signed-off-by: Deepa Dinamani
Cc: Dave Kleikamp
Cc: jfs-discuss...@lists.sourceforge.net
---
fs/jfs/ioctl.c | 2 +-
1 file
All uses of these macros have been replaced by other
time functions.
These macros are also not y2038 safe.
And, all its use cases can be fulfilled by y2038
safe ktime_get_* variants.
Signed-off-by: Deepa Dinamani
Cc: John Stultz
Cc: Thomas Gleixner
Acked-by: John Stultz
---
include/linux
timestamps for cifs is transitioned
to use timespec64.
Signed-off-by: Deepa Dinamani
Cc: Steve French
---
fs/cifs/cifsencrypt.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/cifs/cifsencrypt.c b/fs/cifs/cifsencrypt.c
index 6aeb8d4..b86ce67 100644
--- a/fs/cifs/cifsencrypt.c
x27;s super_block.
The granularity check to call current_fs_time() or
CURRENT_TIME_SEC is not required.
Use current_time() directly to update inode timestamp.
Use timespec_trunc during file system creation, before
the first inode is created.
Signed-off-by: Deepa Dinamani
Cc: Artem Bityutskiy
Cc: A
timespec64 as well.
Signed-off-by: Deepa Dinamani
Cc: Chris Mason
Cc: Josef Bacik
Cc: David Sterba
Cc: linux-bt...@vger.kernel.org
---
fs/btrfs/root-tree.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/btrfs/root-tree.c b/fs/btrfs/root-tree.c
index f1c3086..161118b
range checking is introduced.
This works because alloc_super() fills in the the s_time_gran
in super block to NSEC_PER_SEC.
Also note that filesystem specific times like the birthtime,
creation time that were using same interfaces to obtain time
retain same logistics.
Signed-off-by: Deepa
the thread, changing the function name.
current_fs_time() will be deleted after all the references
to it are replaced by current_time().
Note that timespec_trunc() will also be moved to fs/inode.c
in a separate patch when this will need to be revamped for
bounds checking purposes.
Signed-off
macro will be deleted before merging the
aforementioned change.
Change signature of helper cifs_all_info_to_fattr since it
now needs both super_block and cifs_sb_info.
Note: The inode timestamps read from the server are assumed
to have correct granularity and range.
Signed-off-by: Deepa Dinaman
are being handled in a series separate from transitioning vfs to use.
Changes from v1:
* Change current_fs_time(struct super_block *) to current_time(struct inode *)
* Note that change to add time64_to_tm() is already part of John's
kernel tree: https://lkml.org/lkml/2016/6/17/875 .
Dee
ded to do range checks.
Signed-off-by: Deepa Dinamani
Cc: Jan Kara
Reviewed-by: Jan Kara
---
fs/udf/super.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/udf/super.c b/fs/udf/super.c
index 4942549..134c63a 100644
--- a/fs/udf/super.c
+++ b/fs/udf/super.c
@@
CURRENT_TIME_SEC is not required.
Use current_time() directly to obtain timestamps
unconditionally, and remove ext4_current_time().
Quota files are assumed to be on the same filesystem.
Hence, use current_time() for these files as well.
Signed-off-by: Deepa Dinamani
Cc: "Theodore Ts'o"
Cc: And
On Fri, Jun 17, 2016 at 1:52 PM, John Stultz wrote:
> On Wed, Jun 15, 2016 at 10:44 AM, Deepa Dinamani
> wrote:
>> On Tue, Jun 14, 2016 at 2:18 PM, John Stultz wrote:
>>> On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani
>>> wrote:
>>>> time_to_tm() t
On Tue, Jun 14, 2016 at 2:18 PM, John Stultz wrote:
> On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani
> wrote:
>> time_to_tm() takes time_t as an argument.
>> time_t is not y2038 safe.
>> Add time64_to_tm() that takes time64_t as an argument
>> which is y2038 safe
On Fri, Jun 10, 2016 at 3:19 PM, Arnd Bergmann wrote:
> On Thursday, June 9, 2016 11:45:01 AM CEST Linus Torvalds wrote:
>> On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani
>> wrote:
>> > CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe.
>> > current_fs_
>> >> Documentation/coccinelle.txt suggests using the SPFLAGS
>> >> make variable to pass additional options to spatch.
>> >>
>> >> Reorder the way SPFLAGS is added to FLAGS, to allow
>> >> for options in the SPFLAGS to override the default
>> >> --very-quiet option.
>> >>
>> >> Similarly, rearrage
>> Documentation/coccinelle.txt suggests using the SPFLAGS
>> make variable to pass additional options to spatch.
>>
>> Reorder the way SPFLAGS is added to FLAGS, to allow
>> for options in the SPFLAGS to override the default
>> --very-quiet option.
>>
>> Similarly, rearrage the FLAGS for org or re
allows for overriding of the default --no-show-diff
option through SPFLAGS.
Signed-off-by: Deepa Dinamani
Cc: Julia Lawall
Cc: Gilles Muller
Cc: Nicolas Palix
Cc: Michal Marek
---
scripts/coccicheck | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/coccicheck b
On Fri, Jun 10, 2016 at 3:21 PM, Arnd Bergmann wrote:
> On Wednesday, June 8, 2016 10:04:45 PM CEST Deepa Dinamani wrote:
>> CURRENT_TIME_SEC is not y2038 safe. current_fs_time() will
>> be transitioned to use 64 bit time along with vfs in a
>> separate patch.
>> Ther
On Thu, Jun 9, 2016 at 12:41 AM, Jan Kara wrote:
> On Wed 08-06-16 22:04:50, Deepa Dinamani wrote:
>> Logical Volume Integrity format is described to have the
>> same timestamp format for "Recording Date and time" as
>> the other [a,c,m]timestamps.
>> Hence
On Thu, Jun 9, 2016 at 7:31 AM, Steve Grubb wrote:
> On Wednesday, June 08, 2016 10:05:01 PM Deepa Dinamani wrote:
>> Audit timestamps are recorded in string format into
>> an audit buffer for a given context.
>> These mark the entry timestamps for the syscalls.
>
>>boot_time is represented as a struct timespec.
>>struct timespec and CURRENT_TIME are not y2038 safe.
>>Overall, the plan is to use timespec64 for all internal
>>kernel representation of timestamps.
>>CURRENT_TIME will also be removed.
>>Use struct timespec64 to represent boot_time.
>>And, ktime_
On Thu, Jun 9, 2016 at 12:15 PM, Linus Torvalds
wrote:
> On Thu, Jun 9, 2016 at 12:35 AM, Jan Kara wrote:
>>
>> You create line longer than 80 characters for affs and reiserfs. Please
>> wrap those lines properly.
>
> No, please do *NOT* do things like that.
>
> These kind of mechanical patches s
RRENT_TIME
macro bug fixes are being handled in a series separate from transitioning
vfs to use 64 bit timestamps.
Some reviewers have requested not to change line wrapping only for the
longer function call names, so checkpatch warnings for such cases are
ignored in the patch series.
Deepa Dinamani
super_block.
The granularity check to call current_fs_time() or
CURRENT_TIME_SEC is not required.
Use current_fs_time() to obtain timestamps
unconditionally.
Signed-off-by: Deepa Dinamani
Cc: Artem Bityutskiy
Cc: Adrian Hunter
Cc: linux-...@lists.infradead.org
---
fs/ubifs/dir.c | 10
when range checking is introduced.
This works because alloc_super() fills in the the s_time_gran
in super block to NSEC_PER_SEC.
Also note that filesystem specific times like the birthtime,
creation time that were using same interfaces to obtain time
retain same logistics.
Signed-off-by: Deepa
501 - 600 of 705 matches
Mail list logo
