From owner-freebsd-current Sun Jan 26 08:48:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA14605 for current-outgoing; Sun, 26 Jan 1997 08:48:49 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA14600 for ; Sun, 26 Jan 1997 08:48:47 -0800 (PST) Received: from schizo.dk.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0voXk4-0003vmC; Sun, 26 Jan 97 08:47 PST Received: from critter.dk.tfs.com (critter-home [193.162.32.19]) by schizo.dk.tfs.com (8.8.2/8.7.3) with ESMTP id RAA18204; Sun, 26 Jan 1997 17:47:35 +0100 (MET) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id RAA07585; Sun, 26 Jan 1997 17:48:48 +0100 (MET) To: dg@root.com cc: Luigi Rizzo , swallace@ece.uci.edu, current@FreeBSD.ORG Subject: Re: exec bug In-reply-to: Your message of "Sun, 26 Jan 1997 05:36:03 PST." <199701261336.FAA06928@root.com> Date: Sun, 26 Jan 1997 17:48:48 +0100 Message-ID: <7583.854297328@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199701261336.FAA06928@root.com>, David Greenman writes: > ...and just how do you tell the exec code that a page fault that occured >while it was accessing the image header was "fatal"? The only mechanism we >have for this is signals, and that doesn't work when you're executing in the >kernel like this. Wouldn't it make sense for the image activator to do a couple of probes first to see that the data is actually available ? that way it could fail intelligently ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail.