aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Johnston <markj@FreeBSD.org>2025-06-26 21:19:14 +0000
committerMark Johnston <markj@FreeBSD.org>2026-07-14 23:08:13 +0000
commit4d07fdc1eb0b8ff9ee3b74ac0bceaf07b1c813f0 (patch)
tree029971b3200346ea8f2f21ba8b9f1af3fcfaf81e
parente56cb0b4cc3c48bbf287fc5eba427c66b228acbb (diff)
fibs_test: Mark same_ip_multiple_ifaces_fib0 as expected to fail
The test relies on being able to assign the same interface address to two different tap interfaces; it then removes one of the addresses, which at one point would trigger a kernel panic. Since 361a8395f0b0 it is not possible to assign an address multiple times this way, so the test fails. Just mark it as expected to fail for now: if the kernel's behaviour here changes again, this test might be a useful seatbelt. MFC after: 2 weeks (cherry picked from commit 6bdc9743d8f8c9727e5101d6cb6f2a85a13c5acb)
-rw-r--r--tests/sys/netinet/fibs_test.sh3
1 files changed, 3 insertions, 0 deletions
diff --git a/tests/sys/netinet/fibs_test.sh b/tests/sys/netinet/fibs_test.sh
index 794d22a3882b..2e4a7c3da7db 100644
--- a/tests/sys/netinet/fibs_test.sh
+++ b/tests/sys/netinet/fibs_test.sh
@@ -320,6 +320,9 @@ same_ip_multiple_ifaces_fib0_body()
# Setup the interfaces, then remove one alias. It should not panic.
setup_tap 0 inet ${ADDR} ${MASK0}
TAP0=${TAP}
+ # After commit 361a8395f0b0e6f254fd138798232529679d99f6 it became
+ # an error to assign the same interface address twice.
+ atf_expect_fail "The test results in an ifconfig error and thus spuriously fails"
setup_tap 0 inet ${ADDR} ${MASK1}
TAP1=${TAP}
ifconfig ${TAP1} -alias ${ADDR}