From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 v2] selftests: forwarding: flush neighbours in the locked port MAB test
Date: Tue, 3 Nov 2026 19:31:54 +0200 [thread overview]
Message-ID: <20261103173335.2585426-1-eva.kurchatova@virtuozzo.com> (raw)
locked_port_mab starts with the neighbour entry for 192.0.2.2 that
locked_port_ipv4 left behind, and the locked bridge port then drops
h1's traffic for two pings, long enough for that entry to time out.
The locked ping starts a broadcast resolution, which the port drops as
well. When it fails after the FDB entry is replaced, the next ping has
already queued its first packet and gets "Destination Host
Unreachable", and since ping runs with a deadline, it stops at that
error. The check "Ping did not work after replacing FDB entry" then
fails.
Flush h1's neighbours after replacing the FDB entry, so that the ping
starts a fresh resolution.
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>
---
Changes in v2:
- Flush only in locked_port_mab, the one case where the entry is old
enough to time out while the port is locked; the ipv6 flush hid the
failure by removing that entry early. Keep only the Fixes tag of the
MAB test.
- Describe the resolution.
tools/testing/selftests/net/forwarding/bridge_locked_port.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/net/forwarding/bridge_locked_port.sh b/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
index c62331b2e006..e0bf223d5f46 100755
--- a/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
+++ b/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
@@ -201,6 +201,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 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 17:31 Eva Kurchatova [this message]
2026-11-03 17:36 ` no-reply
2026-11-03 21:46 ` Eva Kurchatova (Virtuozzo)
2026-11-04 20:20 ` Konstantin Khorenko
2026-11-04 20:20 ` 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=20261103173335.2585426-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 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.