netdev - Re: [PATCH net-next 2/2] net: dsa: microchip: add KSZ8 change_tag

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: <20240819104112.gi2egnjbf3b67scu@skbuf>
Date: Mon, 19 Aug 2024 13:41:12 +0300
From: Vladimir Oltean <olteanv@...il.com>
To: vtpieter@...il.com
Cc: Woojung Huh <woojung.huh@...rochip.com>, UNGLinuxDriver@...rochip.com,
	Andrew Lunn <andrew@...n.ch>,
	Florian Fainelli <f.fainelli@...il.com>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Russell King <linux@...linux.org.uk>,
	Pieter Van Trappen <pieter.van.trappen@...n.ch>,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 2/2] net: dsa: microchip: add KSZ8
 change_tag_protocol support

Hi Pieter,

On Mon, Aug 19, 2024 at 12:12:35PM +0200, vtpieter@...il.com wrote:
> From: Pieter Van Trappen <pieter.van.trappen@...n.ch>
> 
> Add support for changing the KSZ8 switches tag protocol. In fact
> these devices can only enable or disable the tail tag, so there's
> really only three supported protocols:
> - DSA_TAG_PROTO_KSZ8795 for KSZ87xx
> - DSA_TAG_PROTO_KSZ9893 for KSZ88x3
> - DSA_TAG_PROTO_NONE
> 
> When disabled, this can be used as a workaround for the 'Common
> pitfalls using DSA setups' [1] to use the conduit network interface as
> a regular one, admittedly forgoing most DSA functionality and using
> the device as an unmanaged switch whilst allowing control
> operations (ethtool, PHY management, WoL).

Concretely, what is it that you wish to accomplish? I see you chose to
ignore my previous NACK due to the lack of a strong justification for
disabling the tagging protocol.
https://lore.kernel.org/netdev/20240801134401.h24ikzuoiakwg4i4@skbuf/

> Implementing the new software-defined DSA tagging protocol tag_8021q
> [2] for these devices seems overkill for this use case at the time
> being.

I think there's a misunderstanding about tag_8021q. It does not disable
the tagging protocol. But rather, it helps you implement a tagging
protocol when the hardware does not want to cooperate. So I don't see
how it would have helped you in your goal (whatever that is), and why
mention it.

tag_8021q exists because it is my goal for DSA_TAG_PROTO_NONE to
eventually disappear. The trend is for drivers to be converted from
DSA_TAG_PROTO_NONE to something else (like DSA_TAG_PROTO_VSC73XX_8021Q),
not the other way around. It's a strong usability concern to not be able
to ping through the port net devices.

At the very least we need consensus among the current DSA maintainers
that accepting 'none' as an alternative tagging protocol is acceptable.