summaryrefslogtreecommitdiffstats
path: root/drivers/s390/crypto
diff options
context:
space:
mode:
authorMartin Schwidefsky2009-07-24 12:39:52 +0200
committerMartin Schwidefsky2009-07-24 12:41:02 +0200
commit1277580fe5dfb5aef84854bdb7983657df00b920 (patch)
tree1cfde8482a43f0f0ba56ac488a4cacf52d89fd61 /drivers/s390/crypto
parent[S390] vdso: fix per cpu area allocation (diff)
downloadkernel-qcow2-linux-1277580fe5dfb5aef84854bdb7983657df00b920.tar.gz
kernel-qcow2-linux-1277580fe5dfb5aef84854bdb7983657df00b920.tar.xz
kernel-qcow2-linux-1277580fe5dfb5aef84854bdb7983657df00b920.zip
[S390] vdso: clock_gettime of CLOCK_THREAD_CPUTIME_ID with noexec=on
The combination of noexec=on and a clock_gettime call with clock id CLOCK_THREAD_CPUTIME_ID is broken. The vdso code switches to the access register mode to get access to the per-cpu data structure to execute the magic ectg instruction. After the ectg instruction the code always switches back to the primary mode but for noexec=on the correct mode is the secondary mode. The effect of the bug is that the user space program looses the access to all mappings without PROT_EXEC, e.g. the stack. The problem is fixed by restoring the mode that has been active before the switch to the access register mode. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'drivers/s390/crypto')
0 files changed, 0 insertions, 0 deletions