Re: [RFC PATCH net-next] net: dsa: microchip: implement multi-bridge support
From: Andrew Lunn
Date: Tue Nov 16 2021 - 08:40:21 EST
> > What logging noise?
> I get this with current ksz driver:
> [ 40.185928] br0: port 2(lan2) entered blocking state
> [ 40.190924] br0: port 2(lan2) entered listening state
> [ 41.043186] br0: port 2(lan2) entered blocking state
> [ 55.512832] br0: port 1(lan1) entered learning state
> [ 61.272802] br0: port 2(lan2) neighbor 8000.ae:1b:91:58:77:8b lost
> [ 61.279192] br0: port 2(lan2) entered listening state
> [ 63.113236] br0: received packet on lan1 with own address as source address (addr:00:0e:cd:00:cd:be, vlan:0)
I would guess that transmission from the CPU is broken in this
case. It could be looking up the destination address in the
translation table and not finding an entry. So it floods the packet
out all interfaces, including the CPU. So the CPU receives its own
packet and gives this warning.
Flooding should exclude where the frame came from.