[PATCH] sys_set_mempolicy() doesnt check if mode < 0
commitba17101b41977f124948e0a7797fdcbb59e19f3e
authorEric Dumazet <dada1@cosmosbay.com>
Tue, 2 Aug 2005 04:11:43 +0000 (1 21:11 -0700)
committerLinus Torvalds <torvalds@g5.osdl.org>
Tue, 2 Aug 2005 04:38:00 +0000 (1 21:38 -0700)
tree0d5e8b860e1294e4e38576624e1909075cb84ea6
parent690dbe1ced143876d8fa56b72310738dbe079d0a
[PATCH] sys_set_mempolicy() doesnt check if mode < 0

A kernel BUG() is triggered by a call to set_mempolicy() with a negative
first argument.  This is because the mode is declared as an int, and the
validity check doesnt check < 0 values.  Alternatively, mode could be
declared as unsigned int or unsigned long.

Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
mm/mempolicy.c