[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250320160045.GI889584@horms.kernel.org>
Date: Thu, 20 Mar 2025 16:00:45 +0000
From: Simon Horman <horms@...nel.org>
To: Petr Machata <petrm@...dia.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Andrew Lunn <andrew+netdev@...n.ch>, netdev@...r.kernel.org,
Ido Schimmel <idosch@...dia.com>, Amit Cohen <amcohen@...dia.com>,
mlxsw@...dia.com
Subject: Re: [PATCH net-next 6/6] selftests: vxlan_bridge: Test flood with
unresolved FDB entry
On Mon, Mar 17, 2025 at 06:37:31PM +0100, Petr Machata wrote:
> From: Amit Cohen <amcohen@...dia.com>
>
> Extend flood test to configure FDB entry with unresolved destination IP,
> check that packets are not sent twice.
>
> Without the previous patch which handles such scenario in mlxsw, the
> tests fail:
>
> $ TESTS='test_flood' ./vxlan_bridge_1d.sh
> Running tests with UDP port 4789
> TEST: VXLAN: flood [ OK ]
> TEST: VXLAN: flood, unresolved FDB entry [FAIL]
> vx2 ns2: Expected to capture 10 packets, got 20.
>
> $ TESTS='test_flood' ./vxlan_bridge_1q.sh
> INFO: Running tests with UDP port 4789
> TEST: VXLAN: flood vlan 10 [ OK ]
> TEST: VXLAN: flood vlan 20 [ OK ]
> TEST: VXLAN: flood vlan 10, unresolved FDB entry [FAIL]
> vx10 ns2: Expected to capture 10 packets, got 20.
> TEST: VXLAN: flood vlan 20, unresolved FDB entry [FAIL]
> vx20 ns2: Expected to capture 10 packets, got 20.
>
> With the previous patch, the tests pass.
>
> Signed-off-by: Amit Cohen <amcohen@...dia.com>
> Reviewed-by: Petr Machata <petrm@...dia.com>
> Reviewed-by: Ido Schimmel <idosch@...dia.com>
> Signed-off-by: Petr Machata <petrm@...dia.com>
Reviewed-by: Simon Horman <horms@...nel.org>
Powered by blists - more mailing lists