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!