netdev - Re: [PATCH net-next v3] net: mvpp2: tai: warn once if we fail to update our timestamp

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: <Z3ejTGIpl8nF1Ku8@hoboy.vegasvil.org>
Date: Fri, 3 Jan 2025 00:43:56 -0800
From: Richard Cochran <richardcochran@...il.com>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>,
	Marcin Wojtas <marcin.s.wojtas@...il.com>,
	Andrew Lunn <andrew+netdev@...n.ch>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3] net: mvpp2: tai: warn once if we fail to
 update our timestamp

On Thu, Jan 02, 2025 at 04:26:04PM +0000, Russell King (Oracle) wrote:

> If we fail to read the clock, that will be because the hardware didn't
> respond to our request to read it, which means the hardware broke in
> some way. We could make mvpp22_tai_tstamp() fail and not provide
> timestamps until we have successfully read the HW clock, but we would
> still want to print a warning to explain why HW timestamps vanish.

Sure, keep the warning, but also block time stamp delivery.

> This is to catch a spurious failure that may only affects an occasoinal
> attempt to read the HW PTP time. Currently, we would never know,
> because the kernel is currently completely silent if that were to ever
> happen.

Is the failure spurious, or is the hardware broken and won't recover?

Thanks,
Richard