From owner-freebsd-current Wed Oct 13 12:24:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 4287F14A25 for ; Wed, 13 Oct 1999 12:24:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00417; Wed, 13 Oct 1999 12:15:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910131915.MAA00417@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: Mike Smith , freebsd-current@freebsd.org Subject: Re: SMP stack faults... In-reply-to: Your message of "Tue, 12 Oct 1999 10:27:40 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Oct 1999 12:15:44 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Just a followup question on my question from a week ago or so.... ther was > indeed a stack overflow I'd guess- I check the code path more carefully > and there was a 2KB stack buffer there (oof)- and removing it seemed to > make the problem go away....So the question here is "Shouldn't this have > been a more obvious fault"? There's probably an argument here for putting a guard page below the UP-mode kernel stack, yes. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message