Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Date: 2007-08-17 10:58:50
Also in:
lkml, netdev
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Date: 2007-08-17 10:58:50
Also in:
lkml, netdev
I wrote:
Nick Piggin wrote:quoted
You might find that these places that appear to need barriers are buggy for other reasons anyway. Can you point to some in-tree code we can have a look at?I could, or could not, if I were through with auditing the code. I remembered one case and posted it (nodemgr_host_thread) which was safe because msleep_interruptible provided the necessary barrier there, and this implicit barrier is not in danger to be removed by future patches.
PS, just in case anybody holds his breath for more example code from me, I don't plan to continue with an actual audit of the drivers I maintain. It's an important issue, but my current time budget will restrict me to look at it ad hoc, per case. (Open bugs have higher priority than potential bugs.) -- Stefan Richter -=====-=-=== =--- =---= http://arcgraph.de/sr/