Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 21 Jul 2002 11:31:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 21 Jul 2002 11:31:19 -0400 Received: from pc2-cwma1-5-cust12.swa.cable.ntl.com ([80.5.121.12]:3830 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Sun, 21 Jul 2002 11:31:19 -0400 Subject: Re: [PATCH] strict VM overcommit From: Alan Cox To: Adrian Bunk Cc: Szakacsits Szabolcs , Robert Love , linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 21 Jul 2002 17:46:35 +0100 Message-Id: <1027269995.16818.106.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 765 Lines: 15 On Sun, 2002-07-21 at 13:46, Adrian Bunk wrote: > With enough stupidity root can always trash his system but if as Robert > says the state of the system will be that "no allocations will succeed" > which seems to be a synonymous for "the system is practically dead" it is > IMHO a good idea to let "swapoff -a return -ENOMEM". In the overcommit mode I already suggested that. An administrator can turn off overcommit protection if he really really needs to swapoff regardless of the consequences (eg failing swap disk) - 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/