KOSAKI Motohiro 0753ba01e1 mm: revert "oom: move oom_adj value" ... The commit 2ff05b2b (oom: move oom_adj value) moveed the oom_adj value to the mm_struct. It was a very good first step for sanitize OOM. However Paul Menage reported the commit makes regression to his job scheduler. Current OOM logic can kill OOM_DISABLED process. Why? His program has the code of similar to the following. ... set_oom_adj(OOM_DISABLE); /* The job scheduler never killed by oom */ ... if (vfork() == 0) { set_oom_adj(0); /* Invoked child can be killed */ execve("foo-bar-cmd"); } .... vfork() parent and child are shared the same mm_struct. then above set_oom_adj(0) doesn't only change oom_adj for vfork() child, it's also change oom_adj for vfork() parent. Then, vfork() parent (job scheduler) lost OOM immune and it was killed. Actually, fork-setting-exec idiom is very frequently used in userland program. We must not break this assumption. Then, this patch revert commit 2ff05b2b and related commit. Reverted commit list --------------------- - commit 2ff05b2b4e (oom: move oom_adj value from task_struct to mm_struct) - commit 4d8b9135c3 (oom: avoid unnecessary mm locking and scanning for OOM_DISABLE) - commit 8123681022 (oom: only oom kill exiting tasks with attached memory) - commit 933b787b57 (mm: copy over oom_adj value at fork time) Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Cc: Paul Menage <menage@google.com> Cc: David Rientjes <rientjes@google.com> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Cc: Rik van Riel <riel@redhat.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Oleg Nesterov <oleg@redhat.com> Cc: Nick Piggin <npiggin@suse.de> Cc: Mel Gorman <mel@csn.ul.ie> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2009-08-18 16:31:13 -07:00
..
allocpercpu.c
backing-dev.c	Fix congestion_wait() sync/async vs read/write confusion	2009-07-10 20:31:53 +02:00
bootmem.c	kmemleak: Add callbacks to the bootmem allocator	2009-07-08 14:25:14 +01:00
bounce.c
debug-pagealloc.c
dmapool.c
fadvise.c
failslab.c
filemap.c
filemap_xip.c
fremap.c
highmem.c
hugetlb.c	hugetlbfs: fix i_blocks accounting	2009-07-29 19:10:35 -07:00
init-mm.c
internal.h
Kconfig	Security/SELinux: seperate lsm specific mmap_min_addr	2009-08-17 15:09:11 +10:00
Kconfig.debug
kmemcheck.c
kmemleak-test.c
kmemleak.c	kmemleak: Protect the seq start/next/stop sequence by rcu_read_lock()	2009-07-29 12:34:58 -07:00
maccess.c
madvise.c
Makefile
memcontrol.c	cgroup avoid permanent sleep at rmdir	2009-07-29 19:10:35 -07:00
memory.c	mm: Pass virtual address to [__]p{te,ud,md}_free_tlb()	2009-07-27 12:10:38 -07:00
memory_hotplug.c
mempolicy.c	mm: make set_mempolicy(MPOL_INTERLEAV) N_HIGH_MEMORY aware	2009-08-07 10:39:55 -07:00
mempool.c	mempool.c: clean up type-casting	2009-08-10 08:31:16 -07:00
migrate.c
mincore.c
mlock.c
mm_init.c
mmap.c	Security/SELinux: seperate lsm specific mmap_min_addr	2009-08-17 15:09:11 +10:00
mmu_notifier.c
mmzone.c
mprotect.c
mremap.c
msync.c
nommu.c	Security/SELinux: seperate lsm specific mmap_min_addr	2009-08-17 15:09:11 +10:00
oom_kill.c	mm: revert "oom: move oom_adj value"	2009-08-18 16:31:13 -07:00
page-writeback.c	Fix congestion_wait() sync/async vs read/write confusion	2009-07-10 20:31:53 +02:00
page_alloc.c	page-allocator: allow too high-order warning messages to be suppressed with __GFP_NOWARN	2009-07-29 19:10:35 -07:00
page_cgroup.c
page_io.c
page_isolation.c
pagewalk.c
pdflush.c
percpu.c
prio_tree.c
quicklist.c
readahead.c
rmap.c
shmem.c
shmem_acl.c
slab.c
slob.c
slub.c	kmemleak: Trace the kmalloc_large* functions in slub	2009-07-08 14:25:14 +01:00
sparse-vmemmap.c
sparse.c
swap.c
swap_state.c
swapfile.c	PM / Hibernate: Replace bdget call with simple atomic_inc of i_count	2009-07-29 21:07:55 +02:00
thrash.c
truncate.c
util.c
vmalloc.c
vmscan.c	Fix congestion_wait() sync/async vs read/write confusion	2009-07-10 20:31:53 +02:00
vmstat.c