On Tue, Aug 06, 2024 at 12:20:38PM +0800, Geliang Tang wrote:
From: Geliang Tang tanggeliang@kylinos.cn
So many "Address not found" messages occur at the end of forwarding tests when using "ip address del" command for an invalid address:
Can you give an example of an invalid address that triggers this message?
TEST: FDB limits interacting with FDB type local [ OK ] Error: ipv4: Address not found.
... ... TEST: IGMPv3 S,G port entry automatic add to a *,G port [ OK ] Error: ipv4: Address not found. Error: ipv6: address not found.
... ... TEST: Isolated port flooding [ OK ] Error: ipv4: Address not found. Error: ipv6: address not found.
... ... TEST: Externally learned FDB entry - ageing & roaming [ OK ] Error: ipv4: Address not found. Error: ipv6: address not found.
I'm unable to reproduce these with net-next and iproute2-next. Please debug this to understand the root cause or provide more details on how to reproduce.
This patch gnores these messages and redirects them to /dev/null in __addr_add_del().
Signed-off-by: Geliang Tang tanggeliang@kylinos.cn
tools/testing/selftests/net/forwarding/lib.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/net/forwarding/lib.sh b/tools/testing/selftests/net/forwarding/lib.sh index ff96bb7535ff..8670b6053cde 100644 --- a/tools/testing/selftests/net/forwarding/lib.sh +++ b/tools/testing/selftests/net/forwarding/lib.sh @@ -839,7 +839,7 @@ __addr_add_del() array=("${@}") for addrstr in "${array[@]}"; do
ip address $add_del $addrstr dev $if_name
ip address $add_del $addrstr dev $if_name &> /dev/null} -- 2.43.0