linux-kernel - Re: [PATCH net v3] net: thunderx: avoid direct MTU assignment after WRITE

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: 
 <175211461350.963219.17128181938751055078.git-patchwork-notify@kernel.org>
Date: Thu, 10 Jul 2025 02:30:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Alok Tiwari <alok.a.tiwari@...cle.com>
Cc: sgoutham@...vell.com, andrew+netdev@...n.ch, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
 netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 darren.kenny@...cle.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net v3] net: thunderx: avoid direct MTU assignment after
 WRITE_ONCE()

Hello:

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

On Sun,  6 Jul 2025 12:43:21 -0700 you wrote:
> The current logic in nicvf_change_mtu() writes the new MTU to
> netdev->mtu using WRITE_ONCE() before verifying if the hardware
> update succeeds. However on hardware update failure, it attempts
> to revert to the original MTU using a direct assignment
> (netdev->mtu = orig_mtu)
> which violates the intended of WRITE_ONCE protection introduced in
> commit 1eb2cded45b3 ("net: annotate writes on dev->mtu from
> ndo_change_mtu()")
> 
> [...]

Here is the summary with links:
  - [net,v3] net: thunderx: avoid direct MTU assignment after WRITE_ONCE()
    https://git.kernel.org/netdev/net/c/849704b8b211

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