netdev - Re: [PATCH net-next 0/2] mlxsw: Set port STP state on bridge enslavement

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]

Date: Wed, 09 Aug 2023 22:40:22 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Petr Machata <petrm@...dia.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, netdev@...r.kernel.org, idosch@...dia.com,
 danieller@...dia.com, mlxsw@...dia.com
Subject: Re: [PATCH net-next 0/2] mlxsw: Set port STP state on bridge enslavement

Hello:

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

On Tue, 8 Aug 2023 15:18:14 +0200 you wrote:
> When the first port joins a LAG that already has a bridge upper, an
> instance of struct mlxsw_sp_bridge_port is created for the LAG to keep
> track of it as a bridge port. The bridge_port's STP state is initialized to
> BR_STATE_DISABLED. This made sense previously, because mlxsw would only
> ever allow a port to join a LAG if the LAG had no uppers. Thus if a
> bridge_port was instantiated, it must have been because the LAG as such is
> joining a bridge, and the STP state is correspondingly disabled.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] mlxsw: Set port STP state on bridge enslavement
    https://git.kernel.org/netdev/net-next/c/a76ca8afd45a
  - [net-next,2/2] selftests: mlxsw: router_bridge_lag: Add a new selftest
    https://git.kernel.org/netdev/net-next/c/aae5bb8d18d8

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