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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <164394481045.31803.6913798555291608482.git-patchwork-notify@kernel.org>
Date:   Fri, 04 Feb 2022 03:20:10 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Guillaume Nault <gnault@...hat.com>
Cc:     davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
        shuah@...nel.org, linux-kselftest@...r.kernel.org, fw@...len.de
Subject: Re: [PATCH net-next] selftests: rtnetlink: Use more sensible tos values

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.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