linux-kernel - Re: [PATCH RFC net-next v3 4/4] net: dsa: add basic initial driver for MxL862xx switches

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: <0d9bca64-75cb-441a-a0f8-6f84362e75d2@lunn.ch>
Date: Tue, 6 Jan 2026 14:11:43 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Daniel Golle <daniel@...rotopia.org>
Cc: Vladimir Oltean <olteanv@...il.com>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Heiner Kallweit <hkallweit1@...il.com>,
	Russell King <linux@...linux.org.uk>,
	Simon Horman <horms@...nel.org>, netdev@...r.kernel.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	Frank Wunderlich <frankwu@....de>, Chad Monroe <chad@...roe.io>,
	Cezary Wilmanski <cezary.wilmanski@...ran.com>,
	Avinash Jayaraman <ajayaraman@...linear.com>,
	Bing tao Xu <bxu@...linear.com>, Liang Xu <lxu@...linear.com>,
	Juraj Povazanec <jpovazanec@...linear.com>,
	"Fanni (Fang-Yi) Chan" <fchan@...linear.com>,
	"Benny (Ying-Tsan) Weng" <yweng@...linear.com>,
	"Livia M. Rosu" <lrosu@...linear.com>,
	John Crispin <john@...ozen.org>
Subject: Re: [PATCH RFC net-next v3 4/4] net: dsa: add basic initial driver
 for MxL862xx switches

> > Do the ports know not to forward packets between each other by default,
> > just to the CPU port? Which setting does that? Is address learning
> > turned off on user ports, since they are operating as standalone?
> 
> The configuration of the switch at this points depends on the default
> configuration which is attached to the firmware blob on the external
> flash chip attached to the switch IC.
> 
> It's an ongoing debate with MaxLinear to find a meaningful way to deal
> with (or rather: flush) that default configuration without needing to
> use all the API.
> 
> In the next series after that one I plan to add all basic bridge and
> bridge-port configuration API calls which can then also be used to
> create "single port bridges" for standalone ports, configure learning,

So does this mean this patch series does allow packets to flow between
ports, not just to the CPU?

That is a fundamental part of DSA, switchdev, linux. netdev interfaces
are separated by default. If this is not true, you should add a big
fat warning to the patchset indicating how it is broken and what the
plan is to fix it.

   Andrew