summaryrefslogtreecommitdiffstats
path: root/mm/mlock.c
diff options
context:
space:
mode:
authorGuillem Jover <guillem.jover@nokia.com>2006-12-06 20:32:24 -0800
committerLinus Torvalds <torvalds@woody.osdl.org>2006-12-07 08:39:21 -0800
commit8fb4fc68ca391862b061b3d358a288ccf6abed39 (patch)
tree5fb67541fb76957260879812d6d21ead6c4e6852 /mm/mlock.c
parent3b17979bda74493633364c2c263b452b7788e350 (diff)
downloadop-kernel-dev-8fb4fc68ca391862b061b3d358a288ccf6abed39.zip
op-kernel-dev-8fb4fc68ca391862b061b3d358a288ccf6abed39.tar.gz
[PATCH] Allow user processes to raise their oom_adj value
Currently a user process cannot rise its own oom_adj value (i.e. unprotecting itself from the OOM killer). As this value is stored in the task structure it gets inherited and the unprivileged childs will be unable to rise it. The EPERM will be handled by the generic proc fs layer, as only processes with the proper caps or the owner of the process will be able to write to the file. So we allow only the processes with CAP_SYS_RESOURCE to lower the value, otherwise it will get an EACCES which seems more appropriate than EPERM. Signed-off-by: Guillem Jover <guillem.jover@nokia.com> Acked-by: Andrea Arcangeli <andrea@novell.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'mm/mlock.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud