lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu,  7 Dec 2017 13:20:46 +0000 (UTC)
From:   Kalle Valo <>
To:     Arnd Bergmann <>
Cc:, Arnd Bergmann <>,
        Johannes Berg <>,
        Arend Van Spriel <>,
        Iain Hunter <>,
        "Reizer, Eyal" <>,
        "David S. Miller" <>,,,
Subject: Re: wlcore: use boottime for fw time sync

Arnd Bergmann <> wrote:

> Using getnstimeofday()/timespec_to_ns() causes an overflow on 32-bit
> architectures in 2038, and may suffer from time jumps due to
> settimeofday() or leap seconds.
> I don't see a reason why this needs to be UTC, so either monotonic
> or boot time would be better here. Assuming that the fw time keeps
> running during suspend, boottime is better than monotonic, and
> ktime_get_boot_ns() will also save the additional conversion to
> nanoseconds.
> Signed-off-by: Arnd Bergmann <>

Patch applied to wireless-drivers-next.git, thanks.

99f6996d4cba wlcore: use boottime for fw time sync


Powered by blists - more mailing lists