From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
Network Development <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: vlan_filtering=1 breaks all traffic (was: Re: warnings from MTU setting on switch ports)
Date: Sat, 5 Dec 2020 15:45:29 +0000 [thread overview]
Message-ID: <20201205154529.GO1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <6424c14e-bd25-2a06-cf0b-f1a07f9a3604@prevas.dk>
On Sat, Dec 05, 2020 at 03:49:02PM +0100, Rasmus Villemoes wrote:
> So, I found out that the problem disappers when I disable
> vlan_filtering, and googling then led me to Russell's patches from
> around March
> (https://patchwork.ozlabs.org/project/netdev/cover/20200218114515.GL18808@shell.armlinux.org.uk/).
>
> But, unlike from what I gather from Russell's description, the problem
> is there whether or not the bridge is created with vlan_filtering
> enabled from the outset or not.
No. My problem is where the bridge is created _without_ vlan_filtering
enabled, and is subsequently enabled. That caused traffic to stop as
soon as vlan_filtering was enabled.
Note that if the bridge were created with vlan_filtering enabled from
the start, there would be no problem.
> Also, cherry-picking 517648c8d1 to
> 5.9.12 doesn't help. The problem also exists on 5.4.80, and (somewhat
> naively) backporting 54a0ed0df496 as well as 517648c8d1 doesn't change that.
I'm not sure what 517648c8d1 is - this isn't a mainline or net-next
commit ID.
54a0ed0df496 is a modification by Vladimir Oltean of my original patch
("net: dsa: mv88e6xxx: fix vlan setup") that fixed it for Marvell DSA,
dropping the Marvell DSA bits of the patch, thereby neutering it for
its intended purpose, while still mostly maintaining the commit
description which implies that it fixes Marvell DSA.
I'm afraid that I've now given up dealing with anything that involves
interaction with the impossible Vladimir Oltean - the problems you are
experiencing are a direct result of Vladimir Oltean's attitudes towards
fellow kernel developers.
You will, however, find that the problem was subsequently fixed by
1fb74191988f on top of 54a0ed0df496, which adds the part that
Vladimir Oltean failed to carry forward. It's all an unnecessary
horrible mess.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-12-05 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 14:30 warnings from MTU setting on switch ports Rasmus Villemoes
2020-11-30 16:04 ` Vladimir Oltean
2020-11-30 22:13 ` Rasmus Villemoes
2020-11-30 22:35 ` Vladimir Oltean
2020-11-30 22:50 ` Rasmus Villemoes
2020-11-30 23:11 ` Andrew Lunn
2020-12-05 14:49 ` vlan_filtering=1 breaks all traffic (was: Re: warnings from MTU setting on switch ports) Rasmus Villemoes
2020-12-05 15:45 ` Russell King - ARM Linux admin [this message]
2020-12-05 16:02 ` vlan_filtering=1 breaks all traffic Rasmus Villemoes
2020-12-05 19:03 ` vlan_filtering=1 breaks all traffic (was: Re: warnings from MTU setting on switch ports) Vladimir Oltean
2020-12-05 20:13 ` vlan_filtering=1 breaks all traffic Rasmus Villemoes
2020-12-06 19:45 ` Vladimir Oltean
2020-12-07 19:43 ` Rasmus Villemoes
2020-12-07 20:15 ` Vladimir Oltean
2020-12-08 2:22 ` 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=20201205154529.GO1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rasmus.villemoes@prevas.dk \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).