From: Vladimir Oltean <olteanv@gmail.com>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
f.fainelli@gmail.com, netdev@vger.kernel.org,
linux@armlinux.org.uk, chris.packham@alliedtelesis.co.nz,
pabeni@redhat.com
Subject: Re: [PATCH v2 net 4/4] net: dsa: mv88e6xxx: Limit rsvd2cpu policy to user ports on 6393X
Date: Thu, 19 Dec 2024 16:14:31 +0200 [thread overview]
Message-ID: <20241219141431.qaosfbhlzk2hcbca@skbuf> (raw)
In-Reply-To: <20241219140541.qmzzheu5ruhjjc63@skbuf>
On Thu, Dec 19, 2024 at 04:05:41PM +0200, Vladimir Oltean wrote:
> On Thu, Dec 19, 2024 at 01:30:43PM +0100, Tobias Waldekranz wrote:
> > For packets with a DA in the IEEE reserved L2 group range, originating
> > from a CPU, forward it as normal, rather than classifying it as
> > management.
>
> Doesn't this break STP? Must be able to inject into ports with an STP
> state other than FORWARDING. I expect that you need a DSA_CMD_FROM_CPU
> tag for that, can't do it with DSA_CMD_FORWARD.
ah, I made a stupid mistake, I though locally generated STP goes through
__br_forward().
I put a WARN_ON_ONCE(skb->protocol == htons(ETH_P_802_2)); in DSA xmit
and convinced myself that this is not the case.
[ 67.115425] br_send_bpdu+0x130/0x2a0
[ 67.119187] br_send_config_bpdu+0x12c/0x170
[ 67.123559] br_transmit_config+0x114/0x180
[ 67.127842] br_config_bpdu_generation+0x6c/0x88
[ 67.132562] br_hello_timer_expired+0x44/0x98
[ 67.137022] call_timer_fn+0xc8/0x300
Please ignore this comment.
next prev parent reply other threads:[~2024-12-19 14:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 12:30 [PATCH v2 net 0/4] net: dsa: mv88e6xxx: Amethyst (6393X) fixes Tobias Waldekranz
2024-12-19 12:30 ` [PATCH v2 net 1/4] net: dsa: mv88e6xxx: Improve I/O related error logging Tobias Waldekranz
2024-12-19 13:41 ` Andrew Lunn
2024-12-19 14:32 ` Vladimir Oltean
2024-12-19 12:30 ` [PATCH v2 net 2/4] net: dsa: mv88e6xxx: Give chips more time to activate their PPUs Tobias Waldekranz
2024-12-19 13:41 ` Andrew Lunn
2024-12-19 12:30 ` [PATCH v2 net 3/4] net: dsa: mv88e6xxx: Never force link on in-band managed MACs Tobias Waldekranz
2024-12-19 13:43 ` Andrew Lunn
2025-01-02 10:31 ` Russell King (Oracle)
2025-01-02 13:06 ` Tobias Waldekranz
2025-01-02 17:08 ` Russell King (Oracle)
2025-01-04 21:37 ` Tobias Waldekranz
2025-01-04 22:09 ` Russell King (Oracle)
2025-01-04 23:16 ` Tobias Waldekranz
2025-01-05 10:41 ` Russell King (Oracle)
2025-01-05 23:30 ` Tobias Waldekranz
2025-01-06 8:20 ` Russell King (Oracle)
2025-01-06 14:39 ` Tobias Waldekranz
2024-12-19 12:30 ` [PATCH v2 net 4/4] net: dsa: mv88e6xxx: Limit rsvd2cpu policy to user ports on 6393X Tobias Waldekranz
2024-12-19 13:44 ` Andrew Lunn
2024-12-19 14:05 ` Vladimir Oltean
2024-12-19 14:14 ` Vladimir Oltean [this message]
2024-12-19 14:34 ` Tobias Waldekranz
2024-12-19 14:42 ` Vladimir Oltean
2024-12-19 14:52 ` Vladimir Oltean
2024-12-19 15:02 ` Tobias Waldekranz
2024-12-19 14:29 ` Vladimir Oltean
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=20241219141431.qaosfbhlzk2hcbca@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tobias@waldekranz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox