Mateusz Guzik a21018063b locks: ensure proper barriers are used with atomic ops when necessary
Unclear how, but the locking routine for mutexes was using the *release*
barrier instead of acquire. This must have been either a copy-pasto or bad
completion.

Going through other uses of atomics shows no barriers in:
- upgrade routines (addressed in this patch)
- sections protected with turnstile locks - this should be fine as necessary
  barriers are in the worst case provided by turnstile unlock

I would like to thank Mark Millard and andreast@ for reporting the problem and
testing previous patches before the issue got identified.

ps.
  .-'---`-.
,'          `.
|             \
|              \
\           _  \
,\  _    ,'-,/-)\
( * \ \,' ,' ,'-)
 `._,)     -',-')
   \/         ''/
    )        / /
   /       ,'-'

Hardware provided by: IBM LTC
2017-03-01 05:06:21 +00:00
..
2016-10-04 17:57:30 +00:00
2016-11-08 23:59:41 +00:00
2017-02-12 09:49:44 +00:00
2017-01-25 20:22:32 +00:00
2017-02-14 13:54:05 +00:00
2017-02-23 19:36:38 +00:00
2017-02-16 21:18:31 +00:00
2017-02-16 21:18:31 +00:00
2016-11-08 23:59:41 +00:00
2017-02-07 16:01:07 +00:00
2016-10-24 16:40:27 +00:00
2017-01-14 04:16:13 +00:00
2016-12-27 20:22:17 +00:00
2016-07-26 17:23:49 +00:00
2016-04-14 17:07:26 +00:00
2017-02-13 09:04:38 +00:00