netdev - Re: [PATCH net-next] net: Add l3mdev index to flow struct and avoid oif reset for port devices

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <164740681044.10029.16814487037983806451.git-patchwork-notify@kernel.org>
Date:   Wed, 16 Mar 2022 05:00:10 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     David Ahern <dsahern@...nel.org>
Cc:     netdev@...r.kernel.org, kuba@...nel.org, davem@...emloft.net,
        greearb@...delatech.com
Subject: Re: [PATCH net-next] net: Add l3mdev index to flow struct and avoid oif
 reset for port devices

Hello:

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

On Mon, 14 Mar 2022 14:45:51 -0600 you wrote:
> The fundamental premise of VRF and l3mdev core code is binding a socket
> to a device (l3mdev or netdev with an L3 domain) to indicate L3 scope.
> Legacy code resets flowi_oif to the l3mdev losing any original port
> device binding. Ben (among others) has demonstrated use cases where the
> original port device binding is important and needs to be retained.
> This patch handles that by adding a new entry to the common flow struct
> that can indicate the l3mdev index for later rule and table matching
> avoiding the need to reset flowi_oif.
> 
> [...]

Here is the summary with links:
  - [net-next] net: Add l3mdev index to flow struct and avoid oif reset for port devices
    https://git.kernel.org/netdev/net-next/c/40867d74c374

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