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
| ||
|
Message-Id: <168491342110.25320.5576599970370486815.git-patchwork-notify@kernel.org> Date: Wed, 24 May 2023 07:30:21 +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, willemdebruijn.kernel@...il.com Subject: Re: [PATCH net-next 0/3] ipv4: Remove RTO_ONLINK from udp, ping and raw sockets. Hello: This series was applied to netdev/net-next.git (main) by David S. Miller <davem@...emloft.net>: On Mon, 22 May 2023 16:37:50 +0200 you wrote: > udp_sendmsg(), ping_v4_sendmsg() and raw_sendmsg() use similar patterns > for restricting their route lookup to on-link hosts. Although they use > slightly different code, they all use RTO_ONLINK to override the least > significant bit of their tos value. > > RTO_ONLINK is used to restrict the route scope even when the scope is > set to RT_SCOPE_UNIVERSE. Therefore it isn't necessary: we can properly > set the scope to RT_SCOPE_LINK instead. > > [...] Here is the summary with links: - [net-next,1/3] ping: Stop using RTO_ONLINK. https://git.kernel.org/netdev/net-next/c/726de790f660 - [net-next,2/3] raw: Stop using RTO_ONLINK. https://git.kernel.org/netdev/net-next/c/c85be08fc4fa - [net-next,3/3] udp: Stop using RTO_ONLINK. https://git.kernel.org/netdev/net-next/c/0e26371db548 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists