Files
kernel_arpi/include/linux
Arnd Bergmann f559935e7c nfs: use time64_t internally
The timestamps for the cache are all in boottime seconds, so they
don't overflow 32-bit values, but the use of time_t is deprecated
because it generally does overflow when used with wall-clock time.

There are multiple possible ways of avoiding it:

- leave time_t, which is safe here, but forces others to
  look into this code to determine that it is over and over.

- use a more generic type, like 'int' or 'long', which is known
  to be sufficient here but loses the documentation of referring
  to timestamps

- use ktime_t everywhere, and convert into seconds in the few
  places where we want realtime-seconds. The conversion is
  sometimes expensive, but not more so than the conversion we
  do today.

- use time64_t to clarify that this code is safe. Nothing would
  change for 64-bit architectures, but it is slightly less
  efficient on 32-bit architectures.

Without a clear winner of the three approaches above, this picks
the last one, favouring readability over a small performance
loss on 32-bit architectures.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2019-12-18 18:07:32 +01:00
..
2019-11-12 11:43:29 -05:00
2019-10-31 16:54:00 +05:30
2019-12-18 18:07:32 +01:00
2019-11-15 23:44:48 +01:00
2019-12-03 07:36:38 -07:00
2019-11-26 10:26:26 +01:00
2019-12-03 11:20:37 +01:00
2019-11-20 09:40:10 +01:00
2019-12-01 12:59:06 -08:00
2019-11-11 09:02:56 +01:00
2019-12-04 19:44:14 -08:00
2019-11-15 13:49:04 -05:00
2019-11-14 19:06:47 -08:00
2019-11-06 08:55:23 -05:00
2019-11-06 08:55:23 -05:00
2019-11-13 19:09:47 +08:00
2019-11-14 13:07:48 +08:00
2019-12-04 19:44:14 -08:00
2019-12-01 06:29:17 -08:00
2019-11-13 12:15:34 -08:00
2019-11-13 00:33:21 +11:00
2019-11-07 07:00:26 +01:00
2019-11-14 12:20:02 +08:00