From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: Fix sys_migrate_pages: Move all pages when invoked from root
Date: Fri, 24 Feb 2006 16:47:33 -0800 [thread overview]
Message-ID: <20060224164733.6d5224a5.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0602241616540.24013@schroedinger.engr.sgi.com>
Christoph Lameter <clameter@engr.sgi.com> wrote:
>
> Currently sys_migrate_pages only moves pages belonging to a process.
> This is okay when invoked from a regular user. But if invoked from
> root it should move all pages as documented in the migrate_pages manpage.
>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
>
> Index: linux-2.6.16-rc4/mm/mempolicy.c
> ===================================================================
> --- linux-2.6.16-rc4.orig/mm/mempolicy.c 2006-02-24 14:32:02.000000000 -0800
> +++ linux-2.6.16-rc4/mm/mempolicy.c 2006-02-24 15:44:24.000000000 -0800
> @@ -940,7 +940,8 @@ asmlinkage long sys_migrate_pages(pid_t
> goto out;
> }
>
> - err = do_migrate_pages(mm, &old, &new, MPOL_MF_MOVE);
> + err = do_migrate_pages(mm, &old, &new,
> + capable(CAP_SYS_ADMIN) ? MPOL_MF_MOVE_ALL : MPOL_MF_MOVE);
> out:
> mmput(mm);
> return err;
What a strange interface. One would expect the syscall to pass in an arg
saying "move my pages" or "move all pages", and then permission checking
will either do that or it will reject it.
As it stands, programs will silently behave differently depending upon
whether root ran them, which is silly.
Also, this check from a few lines earlier:
/*
* Check if this process has the right to modify the specified
* process. The right exists if the process has administrative
* capabilities, superuser priviledges or the same
* userid as the target process.
*/
if ((current->euid != task->suid) && (current->euid != task->uid) &&
(current->uid != task->suid) && (current->uid != task->uid) &&
!capable(CAP_SYS_ADMIN)) {
err = -EPERM;
goto out;
}
appears to be a) somewhat duplicative of your patch and b) a heck of a lot
better way of determining whether to use MF_MOVE versus MF_MOVE_ALL.
--
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>
next prev parent reply other threads:[~2006-02-25 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 0:17 Christoph Lameter
2006-02-25 0:47 ` Andrew Morton [this message]
2006-02-25 0:57 ` Christoph Lameter
2006-02-25 1:15 ` Andrew Morton
2006-02-25 1:27 ` Christoph Lameter
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=20060224164733.6d5224a5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=linux-mm@kvack.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