Skip to contentSkip to conversation

prctl.2, ptrace.2: update pointer to in-kernel Yama documentation

PATCH Applied Eugene Syromyatnikov 2 participants 2 messages Sep 11, 2017 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

PATCH 2/15 prctl.2, ptrace.2: update pointer to in-kernel Yama documentation

Linux commit v4.13-rc1~34^2~30 converted yama documentation (previously resided in Documentation/security/Yama.txt) to ReStructured, along with relocating it to Documentation/amdin-guide/LSM/Yama.rst.

* man2/prctl.2 (.SH DESCRIPTION) <.TP .BR PR_SET_PTRACER>: Amend pointer to Documentation/security/Yama.txt with change introduced in Linux 4.13 (Documentation/admin-guide/LSM/Yama.rst).
* man2/ptrace.2 (.SS /proc/sys/kernel/yama/ptrace_scope): Likewise.

---
 man2/prctl.2  | 6 +++++-
 man2/ptrace.2 | 4 ++++
 2 files changed, 9 insertions(+), 1 deletion(-)
man2/prctl.2 +5 -1
index 88c67a3..046dbcb 100644
@@ -889,7 +889,11 @@ the ptrace restrictions introduced by Yama are effectively disabled for the
 calling process.
 .IP
 For further information, see the kernel source file
-.IR Documentation/security/Yama.txt .
+.IR Documentation/admin\-guide/LSM/Yama.rst
+.\" commit 90bb766440f2147486a2acc3e793d7b8348b0c22
+(or
+.IR Documentation/security/Yama.txt
+before Linux 4.13).
 .TP
 .BR PR_SET_SECCOMP " (since Linux 2.6.23)"
 .\" See http://thread.gmane.org/gmane.linux.kernel/542632
man2/ptrace.2 +4 -0
index dc84d41..cdf503a 100644
@@ -2595,7 +2595,11 @@ operation to declare an additional PID that is allowed to perform
 .BR PTRACE_MODE_ATTACH
 operations on the target.
 See the kernel source file
+.IR Documentation/admin\-guide/LSM/Yama.rst
+.\" commit 90bb766440f2147486a2acc3e793d7b8348b0c22
+(or
 .IR Documentation/security/Yama.txt
+before Linux 4.13)
 for further details.
 .IP
 The use of
Signature · 6 lines
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 20170911030352.GA29790-ZbobWygYI+YXGNroddHbYwC/[email protected]

#2 lore raw
Quoted 3 lines · Eugene Syromyatnikov

Linux commit v4.13-rc1~34^2~30 converted yama documentation (previously resided in Documentation/security/Yama.txt) to ReStructured, along with relocating it to Documentation/amdin-guide/LSM/Yama.rst.

Applied. Thanks!

Cheers,

Michael

Quoted 35 lines

* man2/prctl.2 (.SH DESCRIPTION) <.TP .BR PR_SET_PTRACER>: Amend pointer to Documentation/security/Yama.txt with change introduced in Linux 4.13 (Documentation/admin-guide/LSM/Yama.rst).
* man2/ptrace.2 (.SS /proc/sys/kernel/yama/ptrace_scope): Likewise.

---
  man2/prctl.2  | 6 +++++-
  man2/ptrace.2 | 4 ++++
  2 files changed, 9 insertions(+), 1 deletion(-)
man2/prctl.2 +5 -1
index 88c67a3..046dbcb 100644
@@ -889,7 +889,11 @@ the ptrace restrictions introduced by Yama are effectively disabled for the
  calling process.
  .IP
  For further information, see the kernel source file
-.IR Documentation/security/Yama.txt .
+.IR Documentation/admin\-guide/LSM/Yama.rst
+.\" commit 90bb766440f2147486a2acc3e793d7b8348b0c22
+(or
+.IR Documentation/security/Yama.txt
+before Linux 4.13).
  .TP
  .BR PR_SET_SECCOMP " (since Linux 2.6.23)"
  .\" See http://thread.gmane.org/gmane.linux.kernel/542632
man2/ptrace.2 +0 -0
index dc84d41..cdf503a 100644
@@ -2595,7 +2595,11 @@ operation to declare an additional PID that is allowed to perform
  .BR PTRACE_MODE_ATTACH

man2/ptrace.2 operation to declare an additional PID that is allowed to perform · line 2605

Quoted 10 lines
man2/ptrace.2 +4 -0
  operations on the target.
  See the kernel source file
+.IR Documentation/admin\-guide/LSM/Yama.rst
+.\" commit 90bb766440f2147486a2acc3e793d7b8348b0c22
+(or
  .IR Documentation/security/Yama.txt
+before Linux 4.13)
  for further details.
  .IP
  The use of

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html