netdev - Re: bnxt_en: Incorrect tx timestamp report

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: <6c63cb1a-ba98-47d8-a06a-e8bacf32f45a@lunn.ch>
Date: Thu, 20 Mar 2025 15:48:51 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Kamil Zaripov <zaripov-kamil@...ide.ai>
Cc: netdev@...r.kernel.org
Subject: Re: bnxt_en: Incorrect tx timestamp report

> 2. Is there a method available to read the complete 64-bit PHC
> counter to mitigate the observed problem of 2^48-nanosecond time
> jumps?

The usual workaround is to read the upper part, the lower part, and
the upper part again. If you get two different values for the upper
part, do it all again, until you get consistent values.

Look around other PTP drivers, there is probably code you can
copy/paste.

	Andrew