Date: Sat, 25 Sep 2004 05:44:41 -0700
From: William Lee Irwin III <wli@holomorphy.com>
To: Borislav Petkov <petkov@uni-muenster.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: OOM-killer killed everything
Message-ID: <20040925124441.GM9106@holomorphy.com>
References: <200409251326.13915.petkov@uni-muenster.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200409251326.13915.petkov@uni-muenster.de>
Organization: The Domain of Holomorphy
User-Agent: Mutt/1.5.6+20040722i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1062
Lines: 21

On Sat, Sep 25, 2004 at 01:26:13PM +0200, Borislav Petkov wrote:
> I just started burning an audio cd with cdrecord, ran it as root because of 
> the SUID changes in 2.6.8 when this big bad guy by the name of OOM-killer 
> appeared and started killing everything :) I don't know whether the spurious 
> interrupt issue has something to do with it but according to what I've read 
> on lkml about it until now, it is supposed to be quite harmless. Sysinfo 
> + .config attached.

Usually I only get "Kernel panic: Out of memory and no killable processes..."
from local DoS testcases; I'd be surprised if anyone tripped over such
cases by accident unless they're doing something particularly stressful
(e.g. forking server with zillions of clients) or there's a
particularly outrageously offensive memory leak.


-- wli
-
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/