Eric Dumazet ba17101b41 [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>

2005-08-01 21:38:00 -07:00

..

bootmem.c

…

fadvise.c

…

filemap_xip.c

…

filemap.c

…

filemap.h

…

fremap.c

…

highmem.c

…

hugetlb.c

…

internal.h

…

Kconfig

…

madvise.c

…

Makefile

…

memory.c

[PATCH] x86_64: access of some bad address

2005-08-01 21:38:00 -07:00

mempolicy.c

[PATCH] sys_set_mempolicy() doesnt check if mode < 0

2005-08-01 21:38:00 -07:00

mempool.c

…

mincore.c

…

mlock.c

…

mmap.c

…

mprotect.c

…

mremap.c

…

msync.c

…

nommu.c

…

oom_kill.c

…

page_alloc.c

…

page_io.c

…

page-writeback.c

…

pdflush.c

…

prio_tree.c

…

readahead.c

…

rmap.c

…

shmem.c

…

slab.c

…

sparse.c

…

swap_state.c

…

swap.c

…

swapfile.c

…

thrash.c

…

tiny-shmem.c

…

truncate.c

…

vmalloc.c

…

vmscan.c

…