summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristian Borntraeger <borntraeger@de.ibm.com>2015-09-11 16:23:06 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2015-10-14 14:32:01 +0200
commit33b5881d11c5d852662efb764f5054347296a062 (patch)
tree207368e7cb03f9b3a19f48b4d9a13d64c89d593a
parente0af21c56ddd592b33f74f986a2cb4478b10786e (diff)
downloadlinux-33b5881d11c5d852662efb764f5054347296a062.tar.bz2
s390/vdso: use correct memory barrier
By definition smp_wmb only orders writes against writes. (Finish all previous writes, and do not start any future write). To protect the vdso init code against early reads on other CPUs, let's use a full smp_mb at the end of vdso init. As right now smp_wmb is implemented as full serialization, this needs no stable backport, but this change will be necessary if we reimplement smp_wmb. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
-rw-r--r--arch/s390/kernel/vdso.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/s390/kernel/vdso.c b/arch/s390/kernel/vdso.c
index 0d58269ff425..59eddb0e1a3e 100644
--- a/arch/s390/kernel/vdso.c
+++ b/arch/s390/kernel/vdso.c
@@ -299,7 +299,7 @@ static int __init vdso_init(void)
get_page(virt_to_page(vdso_data));
- smp_wmb();
+ smp_mb();
return 0;
}