From: San Mehat Date: Mon, 26 Apr 2010 22:11:04 +0000 (-0700) Subject: staging: android: lowmemorykiller: Don't try to kill the same pid over and over X-Git-Tag: v3.3-rc1~152^2~101^2~124 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4964cd41cd966502c1e0c5bc929ed15c175f8218;p=pandora-kernel.git staging: android: lowmemorykiller: Don't try to kill the same pid over and over Under certain circumstances, a process can take awhile to handle a sig-kill (especially if it's in a scheduler group with a very low share ratio). When this occurs, lowmemkiller returns to vmscan indicating the process memory has been freed - even though the process is still waiting to die. Since the memory hasn't actually freed, lowmemkiller is called again shortly after, and picks the same process to die; regardless of the fact that it has already been 'scheduled' to die and the memory has already been reported to vmscan as having been freed. Solution is to check fatal_signal_pending() on the selected task, and if it's already pending destruction return; indicating to vmscan that no resources were freed on this pass. Signed-off-by: San Mehat Signed-off-by: Greg Kroah-Hartman --- Reading git-diff-tree failed