[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <3161ed3e-1237-6e80-2f3a-79cb8179a417@linux.vnet.ibm.com>
Date: Mon, 25 Jun 2018 12:30:13 -0700
From: Tyrel Datwyler <tyreld@...ux.vnet.ibm.com>
To: Arnd Bergmann <arnd@...db.de>,
"James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Cc: y2038@...ts.linaro.org, Hannes Reinecke <hare@...e.de>,
Johannes Thumshirn <jthumshirn@...e.de>,
James Smart <jsmart2021@...il.com>,
Jens Axboe <axboe@...nel.dk>,
Steffen Maier <maier@...ux.vnet.ibm.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scsi_transport_fc: use 64-bit timestamps consistently
On 06/18/2018 08:29 AM, Arnd Bergmann wrote:
> The get_seconds() helper returns an 'unsigned long' value, which can
> overflow on 32-bit architectures. Since the interface we pass it into
> already uses a 64-bit type, we can just use ktime_get_real_seconds()
> instead.
>
> While we generally prefer local timestamps in CLOCK_MONOTONIC format
> (ktime_get_seconds), this keeps using the CLOCK_REALTIME version
> in order to maintain compatibility with existing code.
>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> ---
Reviewed-by: Tyrel Datwyler <tyreld@...ux.vnet.ibm.com>
Powered by blists - more mailing lists