linux-kernel - Re: [PATCH net v2] vmxnet3: update MTU after device quiesce

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

Message-Id: 
 <174743703575.4089123.13792303088374756172.git-patchwork-notify@kernel.org>
Date: Fri, 16 May 2025 23:10:35 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Ronak Doshi <ronak.doshi@...adcom.com>
Cc: netdev@...r.kernel.org, stable@...r.kernel.org, guolin.yang@...adcom.com,
 bcm-kernel-feedback-list@...adcom.com, andrew+netdev@...n.ch,
 davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 ronghua@...are.com, sbhatewara@...are.com, bhavesh@...are.com,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH net v2] vmxnet3: update MTU after device quiesce

Hello:

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

On Thu, 15 May 2025 19:04:56 +0000 you wrote:
> Currently, when device mtu is updated, vmxnet3 updates netdev mtu, quiesces
> the device and then reactivates it for the ESXi to know about the new mtu.
> So, technically the OS stack can start using the new mtu before ESXi knows
> about the new mtu.
> 
> This can lead to issues for TSO packets which use mss as per the new mtu
> configured. This patch fixes this issue by moving the mtu write after
> device quiesce.
> 
> [...]

Here is the summary with links:
  - [net,v2] vmxnet3: update MTU after device quiesce
    https://git.kernel.org/netdev/net/c/43f0999af011

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