Re: [PATCH net 0/3] net/mlx5: Preserve speed and state across vport modify commands
| Newsgroups | org.kernel.vger.linux-rdma,org.kernel.vger.linux-kernel,org.kernel.vger.netdev |
|---|---|
| Message-ID | <178725423213.446762.7439713881137610450.git-patchwork-notify@kernel.org> |
Hello: This series was applied to netdev/net.git (main) by Jakub Kicinski <[email protected]>: On Sun, 16 Aug 2026 09:50:12 +0300 you wrote: > Hi, > > The firmware vport modify command bundles both admin state and max tx > speed in a single operation, which requires each side to preserve the > other field when it only intends to change one. > > When modifying max tx speed, the driver already queries the current > admin state and passes it back to avoid overwriting it. However, this > query and the subsequent modify were not atomic, a state change > between the two could cause the modify to overwrite the new state with > a stale value. The fix holds esw->state_lock across the query-modify > sequence. > > [...] Here is the summary with links: - [net,1/3] net/mlx5: E-Switch, use state lock for vport state changes https://git.kernel.org/netdev/net/c/ff0f9b7aa1c7 - [net,2/3] net/mlx5: Move vport DOWN state check out of mlx5_query_vport_max_tx_speed() https://git.kernel.org/netdev/net/c/20f11b5cfa42 - [net,3/3] net/mlx5: E-Switch, preserve max tx speed on vport state modification https://git.kernel.org/netdev/net/c/ad0ae7aefa7a You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html