From owner-freebsd-alpha Wed Feb 23 12:22:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 0206537B9D4 for ; Wed, 23 Feb 2000 12:22:17 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 12NiIN-00003Y-0Y; Wed, 23 Feb 2000 20:22:04 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA32689; Wed, 23 Feb 2000 20:25:01 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 23 Feb 2000 20:22:03 +0000 (GMT) From: Doug Rabson To: John Polstra Cc: alpha@freebsd.org Subject: Re: pcb_onfault bug on alpha? In-Reply-To: <200002231706.JAA38337@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 23 Feb 2000, John Polstra wrote: > In article , > Doug Rabson wrote: > > On Tue, 22 Feb 2000, John Polstra wrote: > > > > > Why doesn't copyerr reset "pcb_onfault" to 0? I think it should. > > > > Yes it should reset pcb_onfault. Scary. > > "Scary" sums up my feelings about it too. :-) Does this look right > as a fix? If so, I'll try to set up a test case and ask Jordan for > approval to commit it. This fix looks good. I'm trying to think what the symptom of this would be. Probably it would only affect a kernel mode SEGFAULT which happened after the copyin/out and turn an ugly panic into an uglier crash. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message