All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "Arun.Ramadoss@microchip.com" <Arun.Ramadoss@microchip.com>
Cc: Claudiu Manoil <claudiu.manoil@nxp.com>,
	"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
	"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
	"vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"idosch@nvidia.com" <idosch@nvidia.com>,
	"linux@rempel-privat.de" <linux@rempel-privat.de>,
	"petrm@nvidia.com" <petrm@nvidia.com>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"hauke@hauke-m.de" <hauke@hauke-m.de>,
	"martin.blumenstingl@googlemail.com" 
	<martin.blumenstingl@googlemail.com>,
	Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Woojung.Huh@microchip.com" <Woojung.Huh@microchip.com>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [RFC PATCH net-next 3/3] net: dsa: never skip VLAN configuration
Date: Fri, 15 Jul 2022 15:26:40 +0000	[thread overview]
Message-ID: <20220715152640.srkhncx3cqfcn2vc@skbuf> (raw)
In-Reply-To: <3527f7f04f97ff21f6243e14a97b342004600c06.camel@microchip.com>

On Fri, Jul 15, 2022 at 09:23:19AM +0000, Arun.Ramadoss@microchip.com wrote:
> Hi Vladimir,
> 
> We tried the following test
> 
> ip link set dev br0 type bridge vlan_filtering 0
> 
> ip link set lan1 master br0
> ip link set lan2 master br0
> 
> bridge vlan add vid 10 dev lan1 pvid untagged
> 
> ==>
> Packet transmitted from Host1 with vid 5 is not received by the Host2 
> Packet transmitted from Host1 with vid 10 is not received by the Host2
> ==> 
> 
> bridge vlan add vid 10 dev lan2 pvid untagged
> 
> ==>
> Packet transmitted from Host1 with vid 5 is received by the Host2 
> Pa
> cket transmitted from Host1 with vid 10 is received by the Host2
> ==> 
> 
> bridge vlan del vid 10 dev lan2
> 
> ==>
> Packet transmitted from Host1 with vid 5 is not received by the Host2 
> Packet transmitted from Host1 with vid 10 is not received by the Host2
> ==> 
> 
> Tried this test before and after applying this patch series. And got
> the same result.
> 
> In summary, packets are dropped when pvid is added to vlan unaware
> bridge. Let me know if anything need to performed on this.

I'm not surprised that forwarding is broken after removing
"ds->configure_vlan_while_not_filtering = false", but I'm surprised that
it's broken even without the change. That suggests that either the flag
wasn't effective in the first place, or that the breakage is caused by
other code paths (not sure which).

Do you get the "skipping configuration of VLAN" warning extack when you
run the "bridge vlan add" command without the patches here? Does
ksz_port_vlan_add() get called at all with VID 10?

  reply	other threads:[~2022-07-15 15:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 17:31 [RFC PATCH net-next 0/3] Delete ds->configure_vlan_while_not_filtering Vladimir Oltean
2022-07-05 17:31 ` [RFC PATCH net-next 1/3] selftests: forwarding: add a vlan_deletion test to bridge_vlan_unaware Vladimir Oltean
2022-07-07 12:13   ` Ido Schimmel
2022-07-07 13:34   ` Martin Blumenstingl
2022-07-07 13:45     ` Vladimir Oltean
2022-07-05 17:31 ` [RFC PATCH net-next 2/3] net: dsa: ar9331: remove ds->configure_vlan_while_not_filtering Vladimir Oltean
2022-07-05 17:31 ` [RFC PATCH net-next 3/3] net: dsa: never skip VLAN configuration Vladimir Oltean
2022-07-06 10:51   ` Arun.Ramadoss
2022-07-06 11:12     ` Vladimir Oltean
2022-07-06 16:33   ` Martin Blumenstingl
2022-07-06 16:45     ` Vladimir Oltean
2022-07-06 19:57       ` Martin Blumenstingl
2022-07-07 22:31         ` Vladimir Oltean
2022-07-08 10:00           ` Martin Blumenstingl
2022-07-08 12:09             ` Vladimir Oltean
2022-07-08 22:27               ` Martin Blumenstingl
2022-07-14 10:46                 ` Arun.Ramadoss
2022-07-14 15:12                   ` Vladimir Oltean
2022-07-15  9:23                     ` Arun.Ramadoss
2022-07-15 15:26                       ` Vladimir Oltean [this message]
2022-07-18 14:34                         ` Arun.Ramadoss
2022-07-18 16:24                           ` Vladimir Oltean
2022-07-26 15:10                             ` Arun.Ramadoss
2022-07-26 17:21                               ` Vladimir Oltean
2022-09-12 15:30                                 ` Arun.Ramadoss
2022-09-12 15:42                                   ` Vladimir Oltean
2022-09-13 10:57                                     ` Arun.Ramadoss
2022-09-13 15:09                                       ` Vladimir Oltean
2022-07-06 20:04       ` Hauke Mehrtens
2022-07-07 22:54         ` 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=20220715152640.srkhncx3cqfcn2vc@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=Arun.Ramadoss@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=vivien.didelot@gmail.com \
    --cc=xiaoliang.yang_1@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 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.