From: Otto Ebeling <oebeling-YEAOTlfEoH7f77WrBdCPMDwVj7d+iGoU@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [patch] Update move_pages(2) manpage to match kernel change
Date: Mon, 21 Aug 2017 22:05:31 +0100 [thread overview]
Message-ID: <e6c853bb0a1dd5f96133a754024f230c@github.mail.kapsi.fi> (raw)
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
Hi,
I recently reported a security bug to the kernel that caused a change to
be made to the move_pages syscall (kernel commit
197e7e521384a23b9e585178f3f11c9fa08274b9), the attached patch updates
the man page to match the new behavior.
Thanks,
Otto Ebeling
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: man.diff --]
[-- Type: text/x-diff; name=man.diff, Size: 592 bytes --]
diff --git a/man2/move_pages.2 b/man2/move_pages.2
index dc3892a..390d23c 100644
--- a/man2/move_pages.2
+++ b/man2/move_pages.2
@@ -47,9 +47,10 @@ indicate constraints on the pages to be moved.
is the ID of the process in which pages are to be moved.
To move pages in another process,
the caller must be privileged
-.RB ( CAP_SYS_NICE )
-or the real or effective user ID of the calling process must match the
-real or saved-set user ID of the target process.
+.RB ( CAP_SYS_PTRACE )
+or otherwise have the permission to use
+.BR ptrace (2)
+on the target process.
If
.I pid
is 0, then
next reply other threads:[~2017-08-21 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 21:05 Otto Ebeling [this message]
[not found] ` <2646ef81-62da-13d5-2793-18149df3659b@gmail.com>
[not found] ` <2646ef81-62da-13d5-2793-18149df3659b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-22 8:14 ` [patch] Update move_pages(2) manpage to match kernel change Otto Ebeling
[not found] ` <94ae97965e44ee23301c31a114577315-YEAOTlfEoH7f77WrBdCPMDwVj7d+iGoU@public.gmane.org>
2017-08-22 22:58 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkh8mcyVuvMYqitB1OO3eo3_fy3gg_fakGmQ+34sYjz1GQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-30 9:27 ` Otto Ebeling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e6c853bb0a1dd5f96133a754024f230c@github.mail.kapsi.fi \
--to=oebeling-yeaotlfeoh7f77wrbdcpmdwvj7d+igou@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox