Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 8 Feb 2002 13:02:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 8 Feb 2002 13:02:04 -0500 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:28689 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Fri, 8 Feb 2002 13:01:57 -0500 Subject: Re: [patch] larger kernel stack (8k->16k) per task To: tigran@veritas.com (Tigran Aivazian) Date: Fri, 8 Feb 2002 18:15:15 +0000 (GMT) Cc: arjanv@redhat.com (Arjan van de Ven), linux-kernel@vger.kernel.org, riel@conectiva.com.br (Rik van Riel), alan@lxorguk.ukuu.org.uk (Alan Cox) In-Reply-To: from "Tigran Aivazian" at Feb 08, 2002 04:59:47 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > to reproduce it with larger stack and then (with aid of /proc/stack) the > offender is found and fixed. I cc'd Alan; if he thinks this is a bad idea > I would be interested to know why. Personal feeling: it would be better to vmalloc the stack in this case and use the existing vmalloc red zones. For 2.5 that should work out ok unlike 2.4 where the scsi and usb will break - 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/