From owner-freebsd-current Tue Feb 27 21:36:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 959B537B71B for ; Tue, 27 Feb 2001 21:36:15 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 10910 invoked by uid 666); 28 Feb 2001 05:48:09 -0000 Received: from i003-146.nv.iinet.net.au (HELO elischer.org) (203.59.3.146) by mail.m.iinet.net.au with SMTP; 28 Feb 2001 05:48:09 -0000 Message-ID: <3A9C8E4C.C19E7F68@elischer.org> Date: Tue, 27 Feb 2001 21:36:12 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Bruce Evans Cc: John Baldwin , Leif Neland , freebsd-current@FreeBSD.ORG, Gary Jennejohn Subject: Re: make kernel failure: pecoff: machine/lock.h References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > On Tue, 27 Feb 2001, John Baldwin wrote: > > > Ok. It may be that we are overflowing the kernel stack and corrupting the pcb > > in the process. One idea atm is to move the pcb off of the stack (since it > > stores persistent data it's a bad place for it anyways) and to add a red zone > > at the bottom of the stack to catch overflows. > > Most of the pcb actually has the same persistence as the kernel stack > (both mainly store the process's context while the process is in the > kernel). But it is silly to put the pcb below the stack instead of > above it. Perhaps the idea is to get a panic sooner when something > is corrupted. I have never understood why the context is not ON the stack. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message