From: Vladimir Oltean <olteanv@gmail.com>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/2] net: dsa: Avoid cross-chip syncing of VLAN filtering
Date: Tue, 25 Jan 2022 02:04:39 +0200 [thread overview]
Message-ID: <20220125000439.c4lbw3ivwunzzz23@skbuf> (raw)
In-Reply-To: <20220124210944.3749235-3-tobias@waldekranz.com>
On Mon, Jan 24, 2022 at 10:09:44PM +0100, Tobias Waldekranz wrote:
> Changes to VLAN filtering are not applicable to cross-chip
> notifications.
Yes, it seems so. In a cross-chip setup, ports will individually leave
the bridge, leaving every switch a chance to unset VLAN filtering.
We have this check in dsa_port_vlan_filtering(), so it's easy to forget
that the function is called more times than actually needed:
if (dsa_port_is_vlan_filtering(dp) == vlan_filtering)
return 0;
Sorry.
> On a system like this:
>
> .-----. .-----. .-----.
> | sw1 +---+ sw2 +---+ sw3 |
> '-1-2-' '-1-2-' '-1-2-'
>
> Before this change, upon sw1p1 leaving a bridge, a call to
> dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.
>
> In this scenario:
>
> .---------. .-----. .-----.
> | sw1 +---+ sw2 +---+ sw3 |
> '-1-2-3-4-' '-1-2-' '-1-2-'
>
> When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be
> called for sw2 and sw3 with a non-existing port - leading to array
> out-of-bounds accesses and crashes on mv88e6xxx.
>
> Fixes: d371b7c92d19 ("net: dsa: Unset vlan_filtering when ports leave the bridge")
> Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
> ---
> net/dsa/switch.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/net/dsa/switch.c b/net/dsa/switch.c
> index 9f9b70d6070a..517cc83d13cc 100644
> --- a/net/dsa/switch.c
> +++ b/net/dsa/switch.c
> @@ -180,9 +180,11 @@ static int dsa_switch_bridge_leave(struct dsa_switch *ds,
> info->sw_index, info->port,
> info->bridge);
>
> - err = dsa_switch_sync_vlan_filtering(ds, info);
> - if (err)
> - return err;
> + if (ds->dst->index == info->tree_index && ds->index == info->sw_index) {
> + err = dsa_switch_sync_vlan_filtering(ds, info);
> + if (err)
> + return err;
> + }
As net-next material, we could probably move this call to
dsa_port_switchdev_unsync_attrs() where there's even a comment that
references it, and do away with the targeted switch check.
>
> return dsa_tag_8021q_bridge_leave(ds, info);
> }
> --
> 2.25.1
>
Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
next prev parent reply other threads:[~2022-01-25 3:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 21:09 [PATCH net 0/2] net: dsa: Avoid cross-chip syncing of VLAN filtering Tobias Waldekranz
2022-01-24 21:09 ` [PATCH net 1/2] net: dsa: Move VLAN filtering syncing out of dsa_switch_bridge_leave Tobias Waldekranz
2022-01-25 0:05 ` Vladimir Oltean
2022-01-24 21:09 ` [PATCH net 2/2] net: dsa: Avoid cross-chip syncing of VLAN filtering Tobias Waldekranz
2022-01-25 0:04 ` Vladimir Oltean [this message]
2022-01-25 18:01 ` [PATCH net 0/2] " Jakub Kicinski
2022-01-25 19:05 ` Tobias Waldekranz
2022-01-25 20:41 ` Jakub Kicinski
2022-01-25 22:20 ` Tobias Waldekranz
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=20220125000439.c4lbw3ivwunzzz23@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@gmail.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).