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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180817162558.GB22210@eeboy>
Date:   Fri, 17 Aug 2018 12:25:58 -0400
From:   Richard Cochran <richardcochran@...il.com>
To:     Bryan.Whitehead@...rochip.com
Cc:     arnd@...db.de,
        UNGLinuxDriver@...rochipTechnology.Mail.Onmicrosoft.com,
        davem@...emloft.net, yuehaibing@...wei.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: lan743x_ptp: convert to ktime_get_clocktai_ts64

On Wed, Aug 15, 2018 at 08:50:03PM +0000, Bryan.Whitehead@...rochip.com wrote:
> Sounds reasonable to me. I will yield to Richard's insight.
> But it would be nice if requirements like these were documented.

I think the only reason for initializing to the system UTC (as most
drivers do) is historical.  The first Intel driver was simply copied.
I've been thinking recently that we should standardize this.  I'm open
for suggestions on how to do this. Remember that the system time is
likely wrong at driver initialization time.

Thanks,
Richard

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ