recompilation.
Suggested-by: Arnd Bergmann <a...@arndb.de>
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
fs/inode.c | 13 +
fs/internal.h | 2 ++
fs/namespace.c | 12
fs/super.c | 7 +++
include/linux/fs
-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
fs/libfs.c | 4
fs/super.c | 2 ++
include/linux/fs.h | 3 +++
include/linux/time64.h | 2 ++
4 files changed, 11 insertions(+)
diff --git a/fs/libfs.c b/fs/libfs.c
index 28d6f35..90ee803 100644
--- a/fs/l
recompilation.
Suggested-by: Arnd Bergmann
Signed-off-by: Deepa Dinamani
---
fs/inode.c | 13 +
fs/internal.h | 2 ++
fs/namespace.c | 12
fs/super.c | 7 +++
include/linux/fs.h | 1 +
include/linux/time64.h | 4
-off-by: Deepa Dinamani
---
fs/libfs.c | 4
fs/super.c | 2 ++
include/linux/fs.h | 3 +++
include/linux/time64.h | 2 ++
4 files changed, 11 insertions(+)
diff --git a/fs/libfs.c b/fs/libfs.c
index 28d6f35..90ee803 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -257,6
ext4 has different overflow limits for max filesystem
timestamps based on the extra bytes available.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
fs/ext4/ext4.h | 4
fs/ext4/super.c | 7 ++-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/fs/ext4/ex
ext4 has different overflow limits for max filesystem
timestamps based on the extra bytes available.
Signed-off-by: Deepa Dinamani
---
fs/ext4/ext4.h | 4
fs/ext4/super.c | 7 ++-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
index
() can be replaced by clamp().
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
fs/utimes.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/fs/utimes.c b/fs/utimes.c
index 32b15b3..052fe5d 100644
--- a/fs/utimes.c
+++ b/fs/utimes.c
@@ -53,6
() can be replaced by clamp().
Signed-off-by: Deepa Dinamani
---
fs/utimes.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/fs/utimes.c b/fs/utimes.c
index 32b15b3..052fe5d 100644
--- a/fs/utimes.c
+++ b/fs/utimes.c
@@ -53,6 +53,7 @@ static int utimes_common
Deepa Dinamani (5):
vfs: Add file timestamp range support
vfs: Add checks for filesystem timestamp limits
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
Deepa Dinamani (5):
vfs: Add file timestamp range support
vfs: Add checks for filesystem timestamp limits
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
for compilation purposes.
Also note that clamp won't do the right thing for timestamps
beyond 2038 on 32-bit machines until the vfs uses timespec64.
After the vfs is transitioned to use timespec64 for timestamps,
clamp_t() can be replaced by clamp().
Signed-off-by: Deepa Dinamani <deepa.
for compilation purposes.
Also note that clamp won't do the right thing for timestamps
beyond 2038 on 32-bit machines until the vfs uses timespec64.
After the vfs is transitioned to use timespec64 for timestamps,
clamp_t() can be replaced by clamp().
Signed-off-by: Deepa Dinamani
---
fs/inode.c | 32
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 <deepa.ker...@gmail.com>
---
fs/f2fs/segment.c | 2 +-
fs/f2fs/segment.h | 5 ++
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
---
fs/f2fs/segment.c | 2 +-
fs/f2fs/segment.h | 5 +++--
2 files changed, 4
make them
y2038 safe. As part of the effort current_time() will be
extended to do range checks.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Reviewed-by: Jan Kara <j...@suse.cz>
Reviewed-by: Arnd Bergmann <a...@arndb.de>
---
fs/udf/super.c | 9 ++---
1 file
make them
y2038 safe. As part of the effort current_time() will be
extended to do range checks.
Signed-off-by: Deepa Dinamani
Reviewed-by: Jan Kara
Reviewed-by: Arnd Bergmann
---
fs/udf/super.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/fs/udf/super.c b/fs/u
and the least max
timestamp supported.
If we take the sysctl approach, then the plan is to also
add a boot param to support initial override of these
checks without recompilation.
Suggested-by: Arnd Bergmann <a...@arndb.de>
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
ext4 has different overflow limits for max filesystem
timestamps based on the extra bytes available.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Cc: "Theodore Ts'o" <ty...@mit.edu>
Cc: Andreas Dilger <adilger.ker...@dilger.ca>
Cc: linux-e...@vger.kernel.
and the least max
timestamp supported.
If we take the sysctl approach, then the plan is to also
add a boot param to support initial override of these
checks without recompilation.
Suggested-by: Arnd Bergmann
Signed-off-by: Deepa Dinamani
---
fs/inode.c | 5 +
fs/internal.h
ext4 has different overflow limits for max filesystem
timestamps based on the extra bytes available.
Signed-off-by: Deepa Dinamani
Cc: "Theodore Ts'o"
Cc: Andreas Dilger
Cc: linux-e...@vger.kernel.org
---
fs/ext4/ext4.h | 4
fs/ext4/super.c | 7 ++-
2 files changed, 10
for compilation purposes.
The actual patch can only be merged after the vfs is
transitioned to use timespec64 for correct operation of
clamp macro. At which point, clamp_t() will be replaced
by clamp().
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
fs/inode.
here as vfs
is not yet using struct timespec64 internally. This is
for compilation purposes only.
The actual patch can only be merged only after vfs is
transitioned to use timespec64 for correct operation of
clamp macro. At which point, clamp_t() will be replaced
by clamp().
Signed-off-by: Deepa
The original thread is at https://lkml.org/lkml/2016/11/2/294
The branch is available at
https://github.com/deepa-hub/vfs.git refs/heads/vfs_timestamp_policy
Changes since v1:
* return EROFS on mount errors
* fix mtime copy/paste error in utimes
Deepa Dinamani (6):
vfs: Add file timestamp
here as vfs
is not yet using struct timespec64 internally. This is
for compilation purposes only.
The actual patch can only be merged only after vfs is
transitioned to use timespec64 for correct operation of
clamp macro. At which point, clamp_t() will be replaced
by clamp().
Signed-off-by: Deepa
The original thread is at https://lkml.org/lkml/2016/11/2/294
The branch is available at
https://github.com/deepa-hub/vfs.git refs/heads/vfs_timestamp_policy
Changes since v1:
* return EROFS on mount errors
* fix mtime copy/paste error in utimes
Deepa Dinamani (6):
vfs: Add file timestamp
for compilation purposes.
The actual patch can only be merged after the vfs is
transitioned to use timespec64 for correct operation of
clamp macro. At which point, clamp_t() will be replaced
by clamp().
Signed-off-by: Deepa Dinamani
---
fs/inode.c | 32 +++-
1 file changed, 31
Note that all the filesystems that have such simple limits
will be initialized in the same patch.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Cc: linux-...@lists.infradead.org
---
fs/afs/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/afs/super.c b/fs/afs/s
Note that all the filesystems that have such simple limits
will be initialized in the same patch.
Signed-off-by: Deepa Dinamani
Cc: linux-...@lists.infradead.org
---
fs/afs/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/afs/super.c b/fs/afs/super.c
index fbdb022..ab00434
-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
fs/libfs.c | 4
fs/super.c | 2 ++
include/linux/fs.h | 3 +++
include/linux/time64.h | 2 ++
4 files changed, 11 insertions(+)
diff --git a/fs/libfs.c b/fs/libfs.c
index 48826d4..f03c904 100644
--- a/fs/l
-off-by: Deepa Dinamani
---
fs/libfs.c | 4
fs/super.c | 2 ++
include/linux/fs.h | 3 +++
include/linux/time64.h | 2 ++
4 files changed, 11 insertions(+)
diff --git a/fs/libfs.c b/fs/libfs.c
index 48826d4..f03c904 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -256,6
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 <deepa.ker...@gmail.com>
---
fs/ufs/ialloc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/
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
---
fs/ufs/ialloc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/ufs/ialloc.c b/fs/ufs
On Fri, Nov 11, 2016 at 10:42 AM, Dave Kleikamp
<dave.kleik...@oracle.com> wrote:
> On 11/11/2016 12:00 PM, Deepa Dinamani wrote:
>> jfs uses nanosecond granularity for filesystem timestamps.
>> Only this assignment is not using nanosecond granularity.
>> Use curr
On Fri, Nov 11, 2016 at 10:42 AM, Dave Kleikamp
wrote:
> On 11/11/2016 12:00 PM, Deepa Dinamani wrote:
>> jfs uses nanosecond granularity for filesystem timestamps.
>> Only this assignment is not using nanosecond granularity.
>> Use current_time() to get the right granulari
() or 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 <deepa.ker...@gmail.com>
Reviewed-by
() or 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
---
fs/ext4
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 <deepa.ker...@gmail.com>
Acked-by: Dave Kleikamp <dave.kleik...@oracle.com>
Revie
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
Acked-by: Dave Kleikamp
Reviewed-by: Arnd Bergmann
---
fs/jfs/ioctl.c | 2 +-
1 file changed, 1
On Sun, Nov 6, 2016 at 12:28 PM, Arnd Bergmann <a...@arndb.de> wrote:
> On Sunday, November 6, 2016 9:44:33 AM CET Deepa Dinamani wrote:
>> I will post xfs tests that validate mount and range checking.
>> I will keep the policy same as what the RFC suggests for now.
>>
On Sun, Nov 6, 2016 at 12:28 PM, Arnd Bergmann wrote:
> On Sunday, November 6, 2016 9:44:33 AM CET Deepa Dinamani wrote:
>> I will post xfs tests that validate mount and range checking.
>> I will keep the policy same as what the RFC suggests for now.
>>
>> Clampi
I will post xfs tests that validate mount and range checking.
I will keep the policy same as what the RFC suggests for now.
Clamping can be verified once vfs is transitioned to using time64_t.
Thanks,
Deepa
I will post xfs tests that validate mount and range checking.
I will keep the policy same as what the RFC suggests for now.
Clamping can be verified once vfs is transitioned to using time64_t.
Thanks,
Deepa
for compilation purposes.
The actual patch can only be merged after the vfs is
transitioned to use timespec64 for correct operation of
clamp macro. At which point, clamp_t() will be replaced
by clamp().
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
fs/inode.
and the least max
timestamp supported.
If we take the sysctl approach, then the plan is to also
add a boot param to support initial override of these
checks without recompilation.
Suggested-by: Arnd Bergmann <a...@arndb.de>
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
ext4 has different overflow limits for max filesystem
timestamps based on the extra bytes available.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Cc: "Theodore Ts'o" <ty...@mit.edu>
Cc: Andreas Dilger <adilger.ker...@dilger.ca>
Cc: linux-e...@vger.kernel.
for compilation purposes.
The actual patch can only be merged after the vfs is
transitioned to use timespec64 for correct operation of
clamp macro. At which point, clamp_t() will be replaced
by clamp().
Signed-off-by: Deepa Dinamani
---
fs/inode.c | 32 +++-
1 file changed, 31
and the least max
timestamp supported.
If we take the sysctl approach, then the plan is to also
add a boot param to support initial override of these
checks without recompilation.
Suggested-by: Arnd Bergmann
Signed-off-by: Deepa Dinamani
---
fs/inode.c | 5 +
fs/internal.h
ext4 has different overflow limits for max filesystem
timestamps based on the extra bytes available.
Signed-off-by: Deepa Dinamani
Cc: "Theodore Ts'o"
Cc: Andreas Dilger
Cc: linux-e...@vger.kernel.org
---
fs/ext4/ext4.h | 4
fs/ext4/super.c | 7 ++-
2 files changed, 10
here as vfs
is not yet using struct timespec64 internally. This is
for compilation purposes only.
The actual patch can only be merged only after vfs is
transitioned to use timespec64 for correct operation of
clamp macro. At which point, clamp_t() will be replaced
by clamp().
Signed-off-by: Deepa
here as vfs
is not yet using struct timespec64 internally. This is
for compilation purposes only.
The actual patch can only be merged only after vfs is
transitioned to use timespec64 for correct operation of
clamp macro. At which point, clamp_t() will be replaced
by clamp().
Signed-off-by: Deepa
Note that all the filesystems that have such simple limits
will be initialized in the same patch.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Cc: linux-...@lists.infradead.org
---
fs/afs/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/afs/super.c b/fs/afs/s
Note that all the filesystems that have such simple limits
will be initialized in the same patch.
Signed-off-by: Deepa Dinamani
Cc: linux-...@lists.infradead.org
---
fs/afs/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/afs/super.c b/fs/afs/super.c
index fbdb022..ab00434
-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
fs/libfs.c | 4
fs/super.c | 2 ++
include/linux/fs.h | 3 +++
include/linux/time64.h | 2 ++
4 files changed, 11 insertions(+)
diff --git a/fs/libfs.c b/fs/libfs.c
index 48826d4..f03c904 100644
--- a/fs/l
-off-by: Deepa Dinamani
---
fs/libfs.c | 4
fs/super.c | 2 ++
include/linux/fs.h | 3 +++
include/linux/time64.h | 2 ++
4 files changed, 11 insertions(+)
diff --git a/fs/libfs.c b/fs/libfs.c
index 48826d4..f03c904 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -256,6
that the
series depends on:
https://lkml.org/lkml/2016/6/9/38 .
This needs reposting to the mailing list.
The branch for the tree along with dependency can be found at
https://github.com/deepa-hub/vfs.git refs/heads/vfs_timestamp_policy
Deepa Dinamani (6):
vfs: Add file timestamp range support
that the
series depends on:
https://lkml.org/lkml/2016/6/9/38 .
This needs reposting to the mailing list.
The branch for the tree along with dependency can be found at
https://github.com/deepa-hub/vfs.git refs/heads/vfs_timestamp_policy
Deepa Dinamani (6):
vfs: Add file timestamp range support
> I think we should do those two things completely independently.
> We need to do something now to preserve the current interfaces
> for the glibc changes that are coming soon [1], and Deepa's
> patches do that (though I now realize the changelog doesn't
> mention the requirement).
I'll update
> I think we should do those two things completely independently.
> We need to do something now to preserve the current interfaces
> for the glibc changes that are coming soon [1], and Deepa's
> patches do that (though I now realize the changelog doesn't
> mention the requirement).
I'll update
> btw, where did you post the libevdev patch? I haven't seen it anywhere I'm
> subscribed to.
The libevdev patch was posted to input-to...@lists.freedesktop.org :
https://www.mail-archive.com/y2038@lists.linaro.org/msg01824.html
-Deepa
> btw, where did you post the libevdev patch? I haven't seen it anywhere I'm
> subscribed to.
The libevdev patch was posted to input-to...@lists.freedesktop.org :
https://www.mail-archive.com/y2038@lists.linaro.org/msg01824.html
-Deepa
>> >> @@ -55,24 +60,24 @@ struct ff_effect_compat {
>> >>
>> >> static inline size_t input_event_size(void)
>> >> {
>> >> - return (in_compat_syscall() && !COMPAT_USE_64BIT_TIME) ?
>> >> - sizeof(struct input_event_compat) : sizeof(struct
>> >> input_event);
>> >> +
>> >> @@ -55,24 +60,24 @@ struct ff_effect_compat {
>> >>
>> >> static inline size_t input_event_size(void)
>> >> {
>> >> - return (in_compat_syscall() && !COMPAT_USE_64BIT_TIME) ?
>> >> - sizeof(struct input_event_compat) : sizeof(struct
>> >> input_event);
>> >> +
On Fri, Oct 28, 2016 at 5:43 AM, Arnd Bergmann <a...@arndb.de> wrote:
> On Monday, October 17, 2016 8:27:32 PM CEST Deepa Dinamani wrote:
>> @@ -55,24 +60,24 @@ struct ff_effect_compat {
>>
>> static inline size_t input_event_size(void)
>> {
>
On Fri, Oct 28, 2016 at 5:43 AM, Arnd Bergmann wrote:
> On Monday, October 17, 2016 8:27:32 PM CEST Deepa Dinamani wrote:
>> @@ -55,24 +60,24 @@ struct ff_effect_compat {
>>
>> static inline size_t input_event_size(void)
>> {
>> - return (in_compat_sy
>> struct timeval is not y2038 safe.
>> All usage of timeval in the kernel will be replaced by
>> y2038 safe structures.
>>
>> struct input_event maintains time for each input event.
>> Real time timestamps are not ideal for input as this
>> time can go backwards as noted in the patch a80b83b7b8
On Wed, Oct 26, 2016 at 7:56 PM, Peter Hutterer
<peter.hutte...@who-t.net> wrote:
> On Mon, Oct 17, 2016 at 08:27:32PM -0700, Deepa Dinamani wrote:
>> struct timeval is not y2038 safe.
>> All usage of timeval in the kernel will be replaced by
>> y2038 safe structure
>> struct timeval is not y2038 safe.
>> All usage of timeval in the kernel will be replaced by
>> y2038 safe structures.
>>
>> struct input_event maintains time for each input event.
>> Real time timestamps are not ideal for input as this
>> time can go backwards as noted in the patch a80b83b7b8
On Wed, Oct 26, 2016 at 7:56 PM, Peter Hutterer
wrote:
> On Mon, Oct 17, 2016 at 08:27:32PM -0700, Deepa Dinamani wrote:
>> struct timeval is not y2038 safe.
>> All usage of timeval in the kernel will be replaced by
>> y2038 safe structures.
>>
>> struct input_ev
> hmm, I'm a bit confused here. This is an in-kernel bit only (passing the
> time through uinput events has no effect). So why do we need an ioctl here?
> it's an in-kernel decision only anyway and the time in the events sent to
> the evdev client should be dictated by what that client sets for
> hmm, I'm a bit confused here. This is an in-kernel bit only (passing the
> time through uinput events has no effect). So why do we need an ioctl here?
> it's an in-kernel decision only anyway and the time in the events sent to
> the evdev client should be dictated by what that client sets for
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 <a...@arndb.de>
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Reviewed-by: A
compatibility.
The structure to maintain input events will be changed
in a different patch.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
---
drivers/input/misc/uinput.c | 56 -
include/linux/uinput.h | 1 +
include/uapi/linux/ui
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
Reviewed-by: Arnd Bergmann
---
drivers/input/evdev.c| 20
compatibility.
The structure to maintain input events will be changed
in a different patch.
Signed-off-by: Deepa Dinamani
---
drivers/input/misc/uinput.c | 56 -
include/linux/uinput.h | 1 +
include/uapi/linux/uinput.h | 3 +++
3 files changed
are sufficient here.
The unit of the delta times is also changed in certain
cases to nanoseconds rather than microseconds. This is
in line with timespec64 which keeps time in nanoseconds.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Reviewed-by: Arnd Bergmann <a...@arndb.de>
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 <deepa.
are sufficient here.
The unit of the delta times is also changed in certain
cases to nanoseconds rather than microseconds. This is
in line with timespec64 which keeps time in nanoseconds.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
---
drivers/input/serio/hil_mlc.c| 37
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
Reviewed
will be merged at the same time.
Changes from v1:
* Updated changes according to review comments.
* Posted userspace library changes that go along with the series.
Deepa Dinamani (4):
uinput: Add ioctl for using monotonic/ boot times
input: evdev: Replace timeval with timespec64
input
will be merged at the same time.
Changes from v1:
* Updated changes according to review comments.
* Posted userspace library changes that go along with the series.
Deepa Dinamani (4):
uinput: Add ioctl for using monotonic/ boot times
input: evdev: Replace timeval with timespec64
input
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
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
of ktime_t for the authsys_parms
stamp field.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Reviewed-by: Arnd Bergmann <a...@arndb.de>
Cc: Trond Myklebust <trond.mykleb...@primarydata.com>
Cc: Anna Schumaker <anna.schuma...@netapp.com>
Cc: linux-...@vger.kernel.
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 +-
4
1024 characters.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Reviewed-by: Arnd Bergmann <a...@arndb.de>
Acked-by: Paul Moore <p...@paul-moore.com>
Acked-by: Richard Guy Briggs <r...@redhat.com>
Cc: Eric Paris <epa...@redhat.com>
Cc: Paul Moore <p..
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
wide enough to accommodate time64_t.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Reviewed-by: Arnd Bergmann <a...@arndb.de>
Cc: Joel Becker <jl...@evilplan.org>
Cc: ocfs2-de...@oss.oracle.com
---
fs/ocfs2/cluster/heartbeat.c | 2 +-
fs/ocfs2/inode.c | 2 +-
wide enough to accommodate time64_t.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
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 changed, 6 insertions(+), 4
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
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
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 <deepa.ker...@gmail.com>
Reviewed-by: Arnd Bergmann <a...@arndb.de>
Cc:
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
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
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
timestamps for cifs is transitioned
to use timespec64.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Reviewed-by: Arnd Bergmann <a...@arndb.de>
Cc: Steve French <sfre...@samba.org>
---
fs/cifs/cifsencrypt.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
di
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
timespec64 as well.
Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
Cc: Chris Mason <c...@fb.com>
Cc: David Sterba <dste...@suse.com>
Cc: Josef Bacik <jba...@fb.com>
Cc: linux-bt...@vger.kernel.org
---
Changes from previous version:
* Separated from the current_ti
timespec64 as well.
Signed-off-by: Deepa Dinamani
Cc: Chris Mason
Cc: David Sterba
Cc: Josef Bacik
Cc: linux-bt...@vger.kernel.org
---
Changes from previous version:
* Separated from the current_time() api series.
* Moved ktime_get_real_ts() outside of spin lock.
fs/btrfs/root-tree.c | 3 ++-
1
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 <deepa.ker...@gmail.com>
Cc: Evgeniy Dushistov <dushis...@mail.ru>
---
fs/ufs/ialloc.c | 6 --
1 fil
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
701 - 800 of 1238 matches
Mail list logo
