From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1] selftests: forwarding: flush neighbours in the bridge locked port test
Date: Tue, 3 Nov 2026 04:12:34 +0200 [thread overview]
Message-ID: <20261103021237.2465704-1-eva.kurchatova@virtuozzo.com> (raw)
While the port drops h1's traffic, h1's neighbour entry for h2 can go
stale and start probes that the port drops too. If that resolution
fails just after the port lets h1's traffic through again, the next
ping gets "Destination Host Unreachable", ping stops at the first
error because a deadline is set, and the test fails with, for example,
"Ping did not work after replacing FDB entry".
Flush h1's neighbours once the port passes its traffic again, so that
the next ping starts a fresh resolution.
Fixes: b2b681a41251 ("selftests: forwarding: tests of locked port feature")
Fixes: 4a331d346996 ("selftests: forwarding: Add MAC Authentication Bypass (MAB) test cases")
https://virtuozzo.atlassian.net/browse/VSTOR-153057
Feature: fix selftests
Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
---
tools/testing/selftests/net/forwarding/bridge_locked_port.sh | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tools/testing/selftests/net/forwarding/bridge_locked_port.sh b/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
index c62331b2e006..461f598638c2 100755
--- a/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
+++ b/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
@@ -105,6 +105,7 @@ locked_port_ipv4()
check_fail $? "Ping worked after locking port, but before adding FDB entry"
bridge fdb add `mac_get $h1` dev $swp1 master static
+ ip neigh flush dev $h1
ping_do $h1 192.0.2.2
check_err $? "Ping did not work after locking port and adding FDB entry"
@@ -135,6 +136,7 @@ locked_port_vlan()
check_fail $? "Ping through vlan worked after locking port, but before adding FDB entry"
bridge fdb add `mac_get $h1` dev $swp1 vlan 100 master static
+ ip neigh flush dev $h1.100
ping_do $h1.100 198.51.100.2
check_err $? "Ping through vlan did not work after locking port and adding FDB entry"
@@ -164,6 +166,7 @@ locked_port_ipv6()
check_fail $? "Ping6 worked after locking port, but before adding FDB entry"
bridge fdb add `mac_get $h1` dev $swp1 master static
+ ip neigh flush dev $h1
ping6_do $h1 2001:db8:1::2
check_err $? "Ping6 did not work after locking port and adding FDB entry"
@@ -201,6 +204,7 @@ locked_port_mab()
check_err $? "Locked FDB entry not created"
bridge fdb replace `mac_get $h1` dev $swp1 master static
+ ip neigh flush dev $h1
ping_do $h1 192.0.2.2
check_err $? "Ping did not work after replacing FDB entry"
--
2.56.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-11-03 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 2:12 Eva Kurchatova [this message]
2026-11-03 2:15 ` no-reply
2026-11-03 2:41 ` Eva Kurchatova (Virtuozzo)
2026-11-03 13:04 ` Konstantin Khorenko
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=20261103021237.2465704-1-eva.kurchatova@virtuozzo.com \
--to=eva.kurchatova@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.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