mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc5 OOM regression
Date: Thu, 2 Mar 2006 02:23:56 -0800	[thread overview]
Message-ID: <20060302022356.5fad2e08.akpm@osdl.org> (raw)
In-Reply-To: <4405F929.2030609@keyaccess.nl>

Rene Herman <rene.herman@keyaccess.nl> wrote:
>
> I was playing with "slabtop" (a /proc/slabinfo display tool) while 
>  running a little memory-eater app in a different xterm:
> 
>  === pig.c
> 
>  #include <stdlib.h>
> 
>  int main(void)
>  {
>  	unsigned char *p;
> 
>  	while ((p = malloc(4096)))
>  		*p = 0;
>  	return 0;
>  }
> 
>  ===
> 
>  I was expecting the oom-killer but instead had X freeze on me entirely. 
>    No keyboard or mouse, and while the machine does still ping in this 
>  state, also no rlogins. This does not happen in 2.6.15.4 -- there the 
>  oom-killer will kill the eater app (sometimes including the xterm it's 
>  in, sometimes not, but not a problem).
> 
>  The 2.6.16-rc5 freeze is "highly repeatable", meaning not always, but 
>  very often. It seems that having for example Firefox loaded increases 
>  the chances of a full freeze, but that might just be chance as well.

crap, thanks.  I would appear to have broken one of Christoph's patches for
him.

--- devel/mm/oom_kill.c~out_of_memory-locking-fix	2006-03-02 02:17:00.000000000 -0800
+++ devel-akpm/mm/oom_kill.c	2006-03-02 02:17:22.000000000 -0800
@@ -355,6 +355,7 @@ retry:
 	}
 
 out:
+	read_unlock(&tasklist_lock);
 	cpuset_unlock();
 	if (mm)
 		mmput(mm);
_


  reply	other threads:[~2006-03-02 10:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01 19:42 Rene Herman
2006-03-02 10:23 ` Andrew Morton [this message]
2006-03-02 16:18   ` Rene Herman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060302022356.5fad2e08.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome