diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2017-11-27 12:57:14 +0100 |
|---|---|---|
| committer | Eric Anholt <eric@anholt.net> | 2017-11-28 16:24:33 -0800 |
| commit | 9107ee6a50b81180f29a9f6588b21917dde2abdd (patch) | |
| tree | 8de00bcb56182a05f3824e1a111869c883911174 /drivers/firmware | |
| parent | 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e (diff) | |
| download | talos-op-linux-9107ee6a50b81180f29a9f6588b21917dde2abdd.tar.gz talos-op-linux-9107ee6a50b81180f29a9f6588b21917dde2abdd.zip | |
firmware: raspberrypi: print time using time64_t
The firmware timestamp is an unsigned 32-bit value, but we copy it into
a signed 32-bit variable, so we can theoretically get an overflow in
the calculation when the timestamp is between 2038 and 2106.
This changes the temporary variable to time64_t and changes the deprecated
time_to_tm() over to time64_to_tm() accordingly.
There is still an overflow in y2106, but that is a limitation of the
firmware interface, not a kernel problem.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Eric Anholt <eric@anholt.net>
Reviewed-by: Eric Anholt <eric@anholt.net>
Diffstat (limited to 'drivers/firmware')
| -rw-r--r-- | drivers/firmware/raspberrypi.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/firmware/raspberrypi.c b/drivers/firmware/raspberrypi.c index dd506cd3a5b8..6692888f04cf 100644 --- a/drivers/firmware/raspberrypi.c +++ b/drivers/firmware/raspberrypi.c @@ -174,7 +174,7 @@ rpi_firmware_print_firmware_revision(struct rpi_firmware *fw) if (ret == 0) { struct tm tm; - time_to_tm(packet, 0, &tm); + time64_to_tm(packet, 0, &tm); dev_info(fw->cl.dev, "Attached to firmware from %04ld-%02d-%02d %02d:%02d\n", |
