linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: otto ebeling <otto.ebeling@iki.fi>,
	mhocko@suse.com, mtk manpages <mtk.manpages@gmail.com>
Cc: linux-mm@kvack.org, clameter@sgi.com, ebiederm@xmission.com,
	w@1wt.eu, keescook@chromium.org, ltp@lists.linux.it
Subject: migrate_pages() of process with same UID in 4.15-rcX
Date: Wed, 10 Jan 2018 10:35:10 -0500 (EST)	[thread overview]
Message-ID: <1394749328.5225281.1515598510696.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1243932888.5206621.1515594158029.JavaMail.zimbra@redhat.com>

Hi,

LTP test migrate_pages02 [1] is failing with 4.15-rcX, presumably as
consequence of:
  313674661925 "Unify migrate_pages and move_pages access checks"

The scenario is that privileged parent forks child, both parent
and child change euid to nobody and then parent tries to migrate
child to different node. Starting with 4.15-rcX it fails with EPERM.

Can anyone comment on accuracy of this sentence from man-pages
after commit 313674661925?

quoting man2/migrate_pages.2:
 "To move pages in another process, 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."

Thanks,
Jan

[1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/migrate_pages/migrate_pages02.c

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

       reply	other threads:[~2018-01-10 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1243932888.5206621.1515594158029.JavaMail.zimbra@redhat.com>
2018-01-10 15:35 ` Jan Stancek [this message]
2018-01-10 16:21   ` migrate_pages() of process with same UID in 4.15-rcX Eric W. Biederman
2018-01-29 13:31     ` Michal Hocko
2018-01-29 13:57       ` Michal Hocko
2018-03-12  9:46         ` 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=1394749328.5225281.1515598510696.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=clameter@sgi.com \
    --cc=ebiederm@xmission.com \
    --cc=keescook@chromium.org \
    --cc=linux-mm@kvack.org \
    --cc=ltp@lists.linux.it \
    --cc=mhocko@suse.com \
    --cc=mtk.manpages@gmail.com \
    --cc=otto.ebeling@iki.fi \
    --cc=w@1wt.eu \
    /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;
as well as URLs for NNTP newsgroup(s).