From owner-freebsd-current Sun Jan 26 04:29:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA05085 for current-outgoing; Sun, 26 Jan 1997 04:29:10 -0800 (PST) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA05080 for ; Sun, 26 Jan 1997 04:29:07 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA27929; Sun, 26 Jan 1997 12:47:07 +0100 From: Luigi Rizzo Message-Id: <199701261147.MAA27929@labinfo.iet.unipi.it> Subject: Re: exec bug To: dg@root.com Date: Sun, 26 Jan 1997 12:47:07 +0100 (MET) Cc: swallace@ece.uci.edu, current@FreeBSD.ORG In-Reply-To: <199701261201.EAA06656@root.com> from "David Greenman" at Jan 26, 97 04:00:42 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >I haven't heard anything about the exec but I reported last week > >when an executable fails to read the image from the media due to a > >read error. > > > >execve() maps the first page to memory and calls exec_aout_imgact() > >which then accesses this page and fails. The system then gets > >a page fault while in kernel mode and dies. Given this description, would this also occur when trying to run a program from an nfs-mounted partition which at some point becomes unavailable ? If not (as I hope!) what is the difference ? Thanks Luigi