From: Andrew Lunn <andrew@lunn.ch>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Vladimir Oltean <olteanv@gmail.com>,
g@pengutronix.de, Woojung Huh <woojung.huh@microchip.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com, kernel@pengutronix.de,
Jakub Kicinski <kuba@kernel.org>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [RFC PATCH net-next] net: dsa: microchip: implement multi-bridge support
Date: Tue, 16 Nov 2021 14:40:06 +0100 [thread overview]
Message-ID: <YZO0tuMtDUIbRfcC@lunn.ch> (raw)
In-Reply-To: <20211116131657.GC16121@pengutronix.de>
> > 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.
Andrew
next prev parent reply other threads:[~2021-11-16 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 11:10 [RFC PATCH net-next] net: dsa: microchip: implement multi-bridge support Oleksij Rempel
2021-11-10 12:36 ` Vladimir Oltean
2021-11-12 7:58 ` Oleksij Rempel
2021-11-15 23:45 ` Vladimir Oltean
2021-11-16 8:39 ` Oleksij Rempel
2021-11-16 12:47 ` Vladimir Oltean
2021-11-16 13:16 ` Oleksij Rempel
2021-11-16 13:40 ` Andrew Lunn [this message]
2021-11-16 13:53 ` Vladimir Oltean
2021-11-16 14:14 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YZO0tuMtDUIbRfcC@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=g@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.