sunrpc: convert to time64_t for expiry

Browse source

Using signed 32-bit types for UTC time leads to the y2038 overflow,
which is what happens in the sunrpc code at the moment.

This changes the sunrpc code over to use time64_t where possible.
The one exception is the gss_import_v{1,2}_context() function for
kerberos5, which uses 32-bit timestamps in the protocol. Here,
we can at least treat the numbers as 'unsigned', which extends the
range from 2038 to 2106.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>

...

This commit is contained in:

Arnd Bergmann 2018-06-07 17:02:50 +02:00

parent 38c4a4cf02

commit 294ec5b87a

8 changed files with 30 additions and 24 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

4

include/linux/sunrpc/gss_api.h

View file

2

include/linux/sunrpc/gss_krb5.h

View file

12

net/sunrpc/auth_gss/gss_krb5_mech.c

View file

8

net/sunrpc/auth_gss/gss_krb5_seal.c

View file

6

net/sunrpc/auth_gss/gss_krb5_unseal.c

View file

16

net/sunrpc/auth_gss/gss_krb5_wrap.c

View file

2

net/sunrpc/auth_gss/gss_mech_switch.c

View file

4

net/sunrpc/auth_gss/svcauth_gss.c

View file