Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 22 Mar 2001 17:17:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 22 Mar 2001 17:16:52 -0500 Received: from navy.csi.cam.ac.uk ([131.111.8.49]:17563 "EHLO navy.csi.cam.ac.uk") by vger.kernel.org with ESMTP id ; Thu, 22 Mar 2001 17:16:26 -0500 Date: Thu, 22 Mar 2001 22:20:22 +0000 (GMT) From: "James A. Sutherland" To: Rik van Riel cc: "Patrick O'Rourke" , , Subject: Re: [PATCH] Prevent OOM from killing init In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 21 Mar 2001, Rik van Riel wrote: > On Wed, 21 Mar 2001, Patrick O'Rourke wrote: > > > Since the system will panic if the init process is chosen by > > the OOM killer, the following patch prevents select_bad_process() > > from picking init. > > One question ... has the OOM killer ever selected init on > anybody's system ? Well, I managed to get the OOM killer killing init once; OTOH, I had just broken MM completely (disabled freeing of pages entirely!) so that doesn't really count, I think :-) > I think that the scoring algorithm should make sure that > we never pick init, unless the system is screwed so badly > that init is broken or the only process left ;) If the system is that badly screwed, killing init is probably the right thing to do, since this should then cause a panic, and thus a reboot if the machine is so configured? James. - 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/