From owner-freebsd-hackers Tue Aug 7 11:44: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 34E6537B40F; Tue, 7 Aug 2001 11:44:03 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.105.118.Dial1.SanJose1.Level3.net [209.244.105.118]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id LAA17157; Tue, 7 Aug 2001 11:43:59 -0700 (PDT) Message-ID: <3B703717.4A50139A@mindspring.com> Date: Tue, 07 Aug 2001 11:44:39 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: "Semen A. Ustimenko" , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel stack size References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > > the kernel stack is a VERY LIMITED resource > basically you have about 4 or 5 Kbytes per process. > if you overflow it you write over your signal information.. > > you should MALLOC space and use a pointer to it.. Would adding an unmapped or read-only guard page be unreasonable? The only thing I could see it doing would be panic'ing, so it's not like it'd be possible to dump the process, without handling the double fault and hoping it doesn't go over 4k of overage (or you'd need 2...N guard pages). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message