John Ogness 3342aa8e6b printk: fix cpu lock ordering
The cpu lock implementation uses a full memory barrier to take
the lock, but no memory barriers when releasing the lock. This
means that changes performed by a lock owner may not be seen by
the next lock owner. This may have been "good enough" for use
by dump_stack() as a serialization mechanism, but it is not
enough to provide proper protection for a critical section.

Correct this problem by using acquire/release memory barriers
for lock/unlock, respectively.

Signed-off-by: John Ogness <john.ogness@linutronix.de>
Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Signed-off-by: Petr Mladek <pmladek@suse.com>
Link: https://lore.kernel.org/r/20210617095051.4808-3-john.ogness@linutronix.de
2021-06-22 09:57:15 +02:00
..
2021-02-21 13:18:26 -08:00
2021-02-21 11:53:06 -08:00
2021-02-21 13:31:43 -08:00
2021-06-22 09:57:15 +02:00
2021-02-21 12:35:04 -08:00
2021-02-21 13:31:43 -08:00
2021-02-21 11:02:48 -08:00
2021-01-06 16:24:59 -08:00
2020-12-15 22:46:19 -08:00
2020-12-17 13:01:31 -08:00
2020-12-14 16:40:27 -08:00
2020-11-14 11:26:04 -08:00
2020-12-17 13:01:31 -08:00
2020-12-14 16:40:27 -08:00
2020-07-27 14:31:12 -04:00
2020-12-01 10:30:28 +00:00
2021-01-24 09:35:28 -08:00
2021-01-22 15:09:42 +01:00
2020-12-27 09:06:10 -08:00
2020-12-19 11:18:38 -08:00
2021-01-29 10:06:46 +05:30
2020-12-14 16:40:27 -08:00
2020-08-19 14:14:12 +02:00
2020-07-07 11:58:59 -05:00
2020-08-19 14:13:20 +02:00