aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2016-10-18 08:00:12 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2016-10-18 08:00:12 +0200
commit3b3d46e7cf1a9949da668db7b686bd968a80f137 (patch)
treef02e7faaa18a9c5ffab38d9623a24b95904c1961
parentc92965c2be8cf05815fbc4351e29b15731bfeb7b (diff)
downloadman-pages-3b3d46e7cf1a9949da668db7b686bd968a80f137.tar.gz
pkeys.7: srcfix
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man7/pkeys.74
1 files changed, 2 insertions, 2 deletions
diff --git a/man7/pkeys.7 b/man7/pkeys.7
index 39e44fc250..fb60f005d5 100644
--- a/man7/pkeys.7
+++ b/man7/pkeys.7
@@ -135,7 +135,7 @@ appropriate for child threads at the time when
.BR clone (2)
is called, or ensure that each child thread can perform its
own initialization of protection key rights.
-
+.\"
.SS Signal Handler Behavior
Each time a signal handler is invoked (including nested signals), the
thread is temporarily given a new, default set of protection key rights
@@ -150,7 +150,7 @@ This signal behavior is unusual and is due to the fact that the x86 PKRU
register (which stores protection key access rights) is managed with the
same hardware mechanism (XSAVE) that manages floating-point registers.
The signal behavior is the same as that of floating point registers.
-
+.\"
.SS Protection Keys system calls
The Linux kernel implements the following pkey-related system calls:
.BR pkey_mprotect (2),