netdev - Re: [PATCH net-next] ipv4: Set the routing scope properly in ip_route_output

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: 
 <170778842639.15795.17520877450881378161.git-patchwork-notify@kernel.org>
Date: Tue, 13 Feb 2024 01:40:26 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Guillaume Nault <gnault@...hat.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
 edumazet@...gle.com, netdev@...r.kernel.org, dsahern@...nel.org,
 jchapman@...alix.com, ap420073@...il.com
Subject: Re: [PATCH net-next] ipv4: Set the routing scope properly in
 ip_route_output_ports().

Hello:

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

On Fri, 9 Feb 2024 17:43:37 +0100 you wrote:
> Set scope automatically in ip_route_output_ports() (using the socket
> SOCK_LOCALROUTE flag). This way, callers don't have to overload the
> tos with the RTO_ONLINK flag, like RT_CONN_FLAGS() does.
> 
> For callers that don't pass a struct sock, this doesn't change anything
> as the scope is still set to RT_SCOPE_UNIVERSE when sk is NULL.
> 
> [...]

Here is the summary with links:
  - [net-next] ipv4: Set the routing scope properly in ip_route_output_ports().
    https://git.kernel.org/netdev/net-next/c/a3522a2edb3f

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