Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 26 Mar 2002 15:25:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 26 Mar 2002 15:25:10 -0500 Received: from twinlark.arctic.org ([204.107.140.52]:1290 "EHLO twinlark.arctic.org") by vger.kernel.org with ESMTP id ; Tue, 26 Mar 2002 15:25:00 -0500 Date: Tue, 26 Mar 2002 12:24:58 -0800 (PST) From: dean gaudet To: Alan Cox cc: Andreas Hartmann , Kernel-Mailingliste Subject: Re: [2.4.18] Security: Process-Killer if machine get's out of memory In-Reply-To: Message-ID: X-comment: visit http://arctic.org/~dean/legal for information regarding copyright and disclaimer. 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 Sun, 24 Mar 2002, Alan Cox wrote: > > > My system cannot (short of a bug) go OOM. Thats what the new overcommit > > > mode 2/3 ensures > > > > How does a process react that doesn't get no more memory? > > Thats up to the process. If a program doesn't handle malloc/mmap/etc > failures then its junk anyway what's the point if you're just going to get signal delivery when you least want it, even when malloc returns non-NULL? it could even be due to stack growth which the compiler is under control of and has no exception mechanism available. i personally prefer to take the signal and exit, it's guaranteed to work in all cases. (hence, apache-1.3 and other multiprocess daemon superiority over threaded and event-driven code, tee hee :) -dean - 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/