[PATCH net-next] selftests: rtnetlink: Use more sensible tos values

[PATCH net-next] selftests: rtnetlink: Use more sensible tos values

[Guillaume Nault]

Using tos 0x1 with 'ip route get <IPv4 address> ...' doesn't test much
of the tos option handling: 0x1 just sets an ECN bit, which is cleared
by inet_rtm_getroute() before doing the fib lookup. Let's use 0x10
instead, which is actually taken into account in the route lookup (and
is less surprising for the reader).

For consistency, use 0x10 for the IPv6 route lookup too (IPv6 currently
doesn't clear ECN bits, but might do so in the future).

Signed-off-by: Guillaume Nault <gnault@redhat.com>
---
No Fixes tag, since this is for net-next and the original test wasn't
actually broken in the first place.

 tools/testing/selftests/net/rtnetlink.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/net/rtnetlink.sh b/tools/testing/selftests/net/rtnetlink.sh
index c9ce3dfa42ee..0900c5438fbb 100755
--- a/tools/testing/selftests/net/rtnetlink.sh
+++ b/tools/testing/selftests/net/rtnetlink.sh
@@ -216,9 +216,9 @@ kci_test_route_get()
 	check_err $?
 	ip route get fe80::1 dev "$devdummy" > /dev/null
 	check_err $?
-	ip route get 127.0.0.1 from 127.0.0.1 oif lo tos 0x1 mark 0x1 > /dev/null
+	ip route get 127.0.0.1 from 127.0.0.1 oif lo tos 0x10 mark 0x1 > /dev/null
 	check_err $?
-	ip route get ::1 from ::1 iif lo oif lo tos 0x1 mark 0x1 > /dev/null
+	ip route get ::1 from ::1 iif lo oif lo tos 0x10 mark 0x1 > /dev/null
 	check_err $?
 	ip addr add dev "$devdummy" 10.23.7.11/24
 	check_err $?
-- 
2.21.3

Re: [PATCH net-next] selftests: rtnetlink: Use more sensible tos values

[patchwork-bot+netdevbpf]

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 2 Feb 2022 16:24:21 +0100 you wrote:
> Using tos 0x1 with 'ip route get <IPv4 address> ...' doesn't test much
> of the tos option handling: 0x1 just sets an ECN bit, which is cleared
> by inet_rtm_getroute() before doing the fib lookup. Let's use 0x10
> instead, which is actually taken into account in the route lookup (and
> is less surprising for the reader).
> 
> For consistency, use 0x10 for the IPv6 route lookup too (IPv6 currently
> doesn't clear ECN bits, but might do so in the future).
> 
> [...]

Here is the summary with links:
  - [net-next] selftests: rtnetlink: Use more sensible tos values
    https://git.kernel.org/netdev/net-next/c/95eb6ef82b73

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html