netdev - Re: [PATCH net-next] liquidio: pass date and time info to NIC firmware

lists.openwall.net		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 linux-hardening linux-cve-announce 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:   Mon, 25 Sep 2017 20:27:23 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     andrew@...n.ch
Cc:     felix.manlunas@...ium.com, netdev@...r.kernel.org,
        raghu.vatsavayi@...ium.com, derek.chickles@...ium.com,
        satananda.burla@...ium.com, manish.awasthi@...ium.com,
        veerasenareddy.burru@...ium.com
Subject: Re: [PATCH net-next] liquidio: pass date and time info to NIC
 firmware

From: Andrew Lunn <andrew@...n.ch>
Date: Sat, 23 Sep 2017 17:16:54 +0200

> On Fri, Sep 22, 2017 at 05:35:18PM -0700, Felix Manlunas wrote:
>> From: Veerasenareddy Burru <veerasenareddy.burru@...ium.com>
> 
> This is kind of interesting. So you do this once. It could be before
> the RTC driver has probed, so it is 1970. It could be before the NTP
> daemon has started, and so the host clock will later jump, or stretch
> time to gain synchronisation.
> 
> It seems like you should be periodically giving the time to the
> firmware, not just once.

Specifically, you really need to send the time/date to the firmware
anytime the system time is updated.