All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: Christoph Lameter <clameter@engr.sgi.com>, ak@suse.de
Cc: linux-mm@kvack.org, michael.kerrisk@gmx.net
Subject: Inconsistent capabilites associated with MPOL_MOVE_ALL
Date: Wed, 15 Mar 2006 01:01:09 +0100 (MET)	[thread overview]
Message-ID: <7277.1142380869@www015.gmx.net> (raw)
In-Reply-To: Pine.LNX.4.64.0603060935300.24016@schroedinger.engr.sgi.com

Andi, Christoph,

In the implementation of migrate_pages() one finds the following 
lines:

err = do_migrate_pages(mm, &old, &new, 
        capable(CAP_SYS_ADMIN) ? MPOL_MF_MOVE_ALL : MPOL_MF_MOVE);

while in the implemantation of mbind() we have:

if ((flags & MPOL_MF_MOVE_ALL( && !capable(CAP_SYS_RESOURCE))
        return -EPERM;

Is it really intended to associate two *different* capabilities 
with the operation of MPOL_MF_MOVE_ALL in this fashion?  At
first glance, it seems rather inconsistent to do so.

Cheers,

Michael

-- 
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 

Want to help with man page maintenance?  
Grab the latest tarball at
ftp://ftp.win.tue.nl/pub/linux-local/manpages/, 
read the HOWTOHELP file and grep the source 
files for 'FIXME'.

--
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:[~2006-03-15  0:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03 16:58 numa_maps update Christoph Lameter
2006-03-04  9:07 ` Andrew Morton
2006-03-04  4:59   ` Andi Kleen
2006-03-04 20:08     ` Christoph Lameter
2006-03-04 20:26       ` Andrew Morton
2006-03-06 16:19         ` Christoph Lameter
2006-03-06 17:37         ` Christoph Lameter
2006-03-15  0:01           ` Michael Kerrisk [this message]
2006-03-15  0:09             ` Inconsistent capabilites associated with MPOL_MOVE_ALL Christoph Lameter
2006-03-15  0:25               ` Michael Kerrisk
2006-03-15  0:33                 ` Christoph Lameter
2006-03-15  0:40                   ` Michael Kerrisk
2006-03-15  0:41                   ` Andrew Morton
2006-03-15  0:53                     ` Christoph Lameter
2006-03-15  1:01                       ` Andrew Morton
2006-03-15  1:07                         ` Michael Kerrisk
2006-03-15  1:12                           ` Michael Kerrisk
2006-03-15  1:16                             ` Christoph Lameter
2006-03-15  1:08                         ` Christoph Lameter
2006-03-15  0:59                     ` Michael Kerrisk
2006-03-15  1:16                       ` Andrew Morton

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=7277.1142380869@www015.gmx.net \
    --to=mtk-manpages@gmx.net \
    --cc=ak@suse.de \
    --cc=clameter@engr.sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=michael.kerrisk@gmx.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.