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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 13 May 2022 11:30:13 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Robert Hancock <robert.hancock@...ian.com> Cc: netdev@...r.kernel.org, radhey.shyam.pandey@...inx.com, davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, michal.simek@...inx.com, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH net-next v7 1/2] net: axienet: Be more careful about updating tx_bd_tail Hello: This series was applied to netdev/net-next.git (master) by David S. Miller <davem@...emloft.net>: On Thu, 12 May 2022 11:18:52 -0600 you wrote: > The axienet_start_xmit function was updating the tx_bd_tail variable > multiple times, with potential rollbacks on error or invalid > intermediate positions, even though this variable is also used in the > TX completion path. Use READ_ONCE where this variable is read and > WRITE_ONCE where it is written to make this update more atomic, and > move the write before the MMIO write to start the transfer, so it is > protected by that implicit write barrier. > > [...] Here is the summary with links: - [net-next,v7,1/2] net: axienet: Be more careful about updating tx_bd_tail https://git.kernel.org/netdev/net-next/c/f0cf4000f586 - [net-next,v7,2/2] net: axienet: Use NAPI for TX completion path https://git.kernel.org/netdev/net-next/c/9e2bc267e780 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists