public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Otto Ebeling <oebeling-YEAOTlfEoH7f77WrBdCPMDwVj7d+iGoU@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch] Update move_pages(2) manpage to match kernel change
Date: Tue, 22 Aug 2017 09:14:58 +0100	[thread overview]
Message-ID: <94ae97965e44ee23301c31a114577315@github.mail.kapsi.fi> (raw)
In-Reply-To: <2646ef81-62da-13d5-2793-18149df3659b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Hi,

> 
>        To  move  pages  in  another process requires the following 
> privi‐
>        leges:
> 
>        *  In kernels up to and including Linux 4.12: the caller  must  
> be
>           privileged  (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.
> 
>        *  The  older rules allowed the caller to discover various 
> virtual
>           address choices made by the  kernel  that  could  lead  to  
> the
>           defeat  of  address-space-layout  randomization  for  a 
> process
>           owned by the same UID as the caller,  the  rules  were  
> changed
>           starting with Linux 4.13.  Since Linux 4.13, permission is 
> gov‐
>           erned by a ptrace access mode PTRACE_MODE_READ_REALCREDS  
> check
>           with respect to the target process; see ptrace(2).
> 
> Look okay?

Thanks for fixing that up, makes sense to document the historical 
behavior! Regarding the references to "Linux 4.13", I wanted to point 
out I got emails that indicate the patch was/will be merged to 
"3.18-stable tree, 4.12-stable tree, 4.4-stable tree, 4.9-stable". See 
e.g. 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=b52c5821b05b33af36b77ba5cfee54818828508f

Not sure how to word this in a man page - maybe something like "4.13, 
and updated versions of 3.18, 4.12, 4.4, and 4.9". What do you think?

Otto
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-08-22  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 21:05 [patch] Update move_pages(2) manpage to match kernel change Otto Ebeling
     [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     ` Otto Ebeling [this message]
     [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=94ae97965e44ee23301c31a114577315@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