linux-kernel - Re: Initial Thoughts on OSI Level 1 Diagnostic for 10BaseT1L Interface

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: <20240827162329.636fe3af@kernel.org>
Date: Tue, 27 Aug 2024 16:23:29 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Oleksij Rempel <o.rempel@...gutronix.de>
Cc: Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>,
 Russell King <linux@...linux.org.uk>, "David S. Miller"
 <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
 <pabeni@...hat.com>, kernel@...gutronix.de, linux-kernel@...r.kernel.org,
 netdev@...r.kernel.org, Maxime Chevallier <maxime.chevallier@...tlin.com>,
 Vladimir Oltean <vladimir.oltean@....com>, Marc Kleine-Budde
 <mkl@...gutronix.de>, Florian Fainelli <f.fainelli@...il.com>,
 Köry Maincent <kory.maincent@...tlin.com>,
 thomas.petazzoni@...tlin.com, jlu@...gutronix.de
Subject: Re: Initial Thoughts on OSI Level 1 Diagnostic for 10BaseT1L
 Interface

On Tue, 27 Aug 2024 07:13:55 +0200 Oleksij Rempel wrote:
> I'd like to share my initial thoughts on how to approach network OSI
> Layer 1 diagnostics for projects using the 10BaseT1L interface. I
> believe this concept could be made more generic and eventually included
> in the kernel documentation. The aim is to help developers like myself
> prioritize tasks more effectively.
> 
> The primary focus of this concept is on embedded systems where human
> interaction isn't feasible, meaning all interfaces should be
> machine-readable. For instance, a flight-recorder application could
> gather as much diagnostic data as possible for later analysis.

Having an open source form of that would be great. Most large operators
probably end up building their own triaging and failure classification
tools.

> At this point, the concept is targeting existing diagnostic interfaces,
> but it may also highlight the need for new ones.

Can't comment on T1L specifics myself but +1 for adding such guides
under Documentation/.