netdev - Re: [RFC PATCH net-next] ptp: Introduce PTP_SYS_OFFSET_EXTENDED

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]

Message-ID: <3f722a52642dc42ad8d5e23ab06c14050d7bf8a6.camel@infradead.org>
Date: Fri, 25 Jul 2025 11:25:24 +0200
From: David Woodhouse <dwmw2@...radead.org>
To: Richard Cochran <richardcochran@...il.com>, David Arinzon
	 <darinzon@...zon.com>
Cc: David Miller <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, 
 Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
 "Woodhouse, David" <dwmw@...zon.com>,  Andrew Lunn <andrew@...n.ch>,
 Miroslav Lichvar <mlichvar@...hat.com>, Thomas Gleixner
 <tglx@...utronix.de>,  netdev@...r.kernel.org, "Machulsky, Zorik"
 <zorik@...zon.com>, "Matushevsky, Alexander" <matua@...zon.com>, Saeed
 Bshara <saeedb@...zon.com>, "Wilson, Matt" <msw@...zon.com>,  "Liguori,
 Anthony" <aliguori@...zon.com>, "Bshara, Nafea" <nafea@...zon.com>,
 "Schmeilin, Evgeny" <evgenys@...zon.com>, "Belgazal, Netanel"
 <netanel@...zon.com>, "Saidi, Ali" <alisaidi@...zon.com>, "Herrenschmidt,
 Benjamin" <benh@...zon.com>,  "Kiyanovski, Arthur" <akiyano@...zon.com>,
 "Dagan, Noam" <ndagan@...zon.com>, "Bernstein, Amit" <amitbern@...zon.com>,
 "Ostrovsky, Evgeny" <evostrov@...zon.com>,  "Tabachnik, Ofir"
 <ofirt@...zon.com>, Julien Ridoux <ridouxj@...zon.com>, Josh Levinson
 <joshlev@...zon.com>
Subject: Re: [RFC PATCH net-next] ptp: Introduce
 PTP_SYS_OFFSET_EXTENDED_TRUSTED ioctl

On Thu, 2025-07-24 at 21:09 -0700, Richard Cochran wrote:
> On Thu, Jul 24, 2025 at 02:56:56PM +0300, David Arinzon wrote:
> 
> > The first objective focuses on the use case where the PHC device
> > is fully managed. The ENA driver, for example, exposes a PHC
> > device, whose synchronization status and quality is maintained
> > without any user-space application. This new ioctl reports on the
> > clock accuracy and status of the PHC device to user-space
> > applications, where ptp4l and similar are not available.
> 
> This seems pretty rare.  I can't think of any other hardware that
> makes claims about synchronization quality.
> 
> So this ioctl would be just for one device.

The vmclock enlightenment also exposes the same information.

David, your RFC should probably have included that implementation
shouldn't it? 

Download attachment "smime.p7s" of type "application/pkcs7-signature" (5069 bytes)