DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:from:to:subject:date:user-agent:organization:mime-version:content-type:content-transfer-encoding:content-disposition:message-id;
        b=GGm2/x0pOo5wCEUgNTBXoUP2ApdWZJzmgFDF/vpEd/jVzvq9D/BwH/rLdj8NbviFR0yAOu17v07bgutOUX2idwbe4A8s0SdaOhnwmQesMLjExmvRiKJKxeEep+0KZCSRQ3f84KMy4l2dn1dB70Ki/G2ImsD1q8DdFydkRtLlFSs=
From: Vicente Feito <vicente.feito@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: oom_killer.c - oom_kill_task and __oom_kill_task question
Date: Fri, 25 Feb 2005 15:32:42 +0000
User-Agent: KMail/1.7.1
Organization: none
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200502251532.42819.vicente.feito@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 613
Lines: 12

Why is it that p->mm it's checked inside oom_kill_task and again in 
__oom_kill_task? Cause __oom_kill_task it's called in case p->mm not null and 
not &init_mm, otherwise it just returns NULL, this has been bothering me, 
I've patched with the last rc5 and it's still there, why?
Is there a chance a process can grow an mm area between one call and another?

Vicente.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/