From owner-freebsd-current Tue Feb 27 20:58:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id C9CAD37B71B; Tue, 27 Feb 2001 20:58:49 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id PAA14790; Wed, 28 Feb 2001 15:58:46 +1100 Date: Wed, 28 Feb 2001 15:58:39 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Leif Neland , freebsd-current@FreeBSD.ORG, Gary Jennejohn Subject: Re: make kernel failure: pecoff: machine/lock.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message