netdev - Re: [PATCH net v3 1/2] ip: fix dflt addr selection for connected nexthop

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 for Android: free password hash cracker in your pocket

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

Message-Id: <165780421418.729.15886797244518922619.git-patchwork-notify@kernel.org>
Date:   Thu, 14 Jul 2022 13:10:14 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Nicolas Dichtel <nicolas.dichtel@...nd.com>
Cc:     davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
        edumazet@...gle.com, dsahern@...nel.org,
        gregkh@...uxfoundation.org, netdev@...r.kernel.org,
        linux-kselftest@...r.kernel.org, stable@...r.kernel.org,
        edwin.brossette@...nd.com
Subject: Re: [PATCH net v3 1/2] ip: fix dflt addr selection for connected nexthop

Hello:

This series was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@...hat.com>:

On Wed, 13 Jul 2022 13:48:52 +0200 you wrote:
> When a nexthop is added, without a gw address, the default scope was set
> to 'host'. Thus, when a source address is selected, 127.0.0.1 may be chosen
> but rejected when the route is used.
> 
> When using a route without a nexthop id, the scope can be configured in the
> route, thus the problem doesn't exist.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/2] ip: fix dflt addr selection for connected nexthop
    https://git.kernel.org/netdev/net/c/747c14307214
  - [net,v3,2/2] selftests/net: test nexthop without gw
    https://git.kernel.org/netdev/net/c/cd72e61bad14

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