linux-kernel - Re: [PATCH net v1 1/2] octeon_ep: avoid compiler and IQ/OQ reordering

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

Message-ID: <eed3d1c1-7b7d-4aea-a816-2046cfa88529@redhat.com>
Date: Mon, 29 Dec 2025 17:15:26 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Vimlesh Kumar <vimleshk@...vell.com>, netdev@...r.kernel.org,
 linux-kernel@...r.kernel.org
Cc: sedara@...vell.com, srasheed@...vell.com, hgani@...vell.com,
 Veerasenareddy Burru <vburru@...vell.com>,
 Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
 <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>, Satananda Burla <sburla@...vell.com>,
 Abhijit Ayarekar <aayarekar@...vell.com>
Subject: Re: [PATCH net v1 1/2] octeon_ep: avoid compiler and IQ/OQ reordering

On 12/19/25 8:29 AM, Vimlesh Kumar wrote:
> Utilize READ_ONCE and WRITE_ONCE APIs for IO queue Tx/Rx
> variable access to prevent compiler optimization and reordering.
> Additionally, ensure IO queue OUT/IN_CNT registers are flushed
> by performing a read-back after writing.

Please explain why such _ONCE() annotation are required, and what could
be reordered otherwise.

I don't think they are needed,

/P