netdev - Re: [PATCH net-next 5/5] ptp: start virtual clocks at current system time.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220127220116.GB26514@hoboy.vegasvil.org>
Date:   Thu, 27 Jan 2022 14:01:16 -0800
From:   Richard Cochran <richardcochran@...il.com>
To:     Miroslav Lichvar <mlichvar@...hat.com>
Cc:     netdev@...r.kernel.org, Yangbo Lu <yangbo.lu@....com>
Subject: Re: [PATCH net-next 5/5] ptp: start virtual clocks at current system
 time.

On Thu, Jan 27, 2022 at 12:45:36PM +0100, Miroslav Lichvar wrote:
> When a virtual clock is being created, initialize the timecounter to the
> current system time instead of the Unix epoch to avoid very large steps
> when the clock will be synchronized.

I think we agreed that, going forward, new PHC drivers should start at
zero (1970) instead of TAI - 37.

Thanks,
Richard