linux-kernel - Re: net: r8169: a question of memory barrier in the r8169 driver

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]

Date:   Fri, 19 Jan 2018 02:11:18 +0100
From:   Francois Romieu <romieu@...zoreil.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Jia-Ju Bai <baijiaju1990@...il.com>, nic_swsd@...ltek.com,
        alexander.h.duyck@...hat.com, David Miller <davem@...emloft.net>,
        dhowells@...hat.com, paulmck@...ux.vnet.ibm.com,
        will.deacon@....com, netdev@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: net: r8169: a question of memory barrier in the r8169 driver

Peter Zijlstra <peterz@...radead.org> :
[...]
> There is only 1 variable afaict. Memory barriers need at least 2 in
> order to be able to do _anything_.

I don't get your point: why don't {cur_tx, dirty_tx} qualify as said
two variables ?

-- 
Ueimor