David Rientjes b259fbde0a mm: update alloc_flags after oom killer has been called
It is possible for the oom killer to select current as the task to kill.
When this happens, alloc_flags needs to be updated accordingly to set
ALLOC_NO_WATERMARKS so the subsequent allocation attempt may use memory
reserves as the result of its thread having TIF_MEMDIE set if the
allocation is not __GFP_NOMEMALLOC.

Acked-by: Mel Gorman <mel@csn.ul.ie>
Signed-off-by: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-09-22 07:17:27 -07:00
..
2009-04-01 08:59:13 -07:00
2009-09-22 07:17:27 -07:00
2009-06-16 19:47:28 -07:00
2009-06-16 19:47:40 -07:00
2009-09-18 09:48:52 -07:00
2009-08-10 08:31:16 -07:00
2009-09-22 07:17:27 -07:00
2008-07-28 16:30:21 -07:00
2008-06-12 18:05:41 -07:00
2007-10-20 01:27:18 +02:00
2009-09-22 07:17:26 -07:00
2009-06-29 09:57:10 +03:00
2009-06-23 12:50:05 -07:00
2009-09-22 07:17:27 -07:00