From owner-freebsd-current Sun Jan 26 04:39:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA05410 for current-outgoing; Sun, 26 Jan 1997 04:39:21 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA05404 for ; Sun, 26 Jan 1997 04:39:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id EAA06801; Sun, 26 Jan 1997 04:39:11 -0800 (PST) Message-Id: <199701261239.EAA06801@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Luigi Rizzo cc: swallace@ece.uci.edu, current@FreeBSD.ORG Subject: Re: exec bug In-reply-to: Your message of "Sun, 26 Jan 1997 12:47:07 +0100." <199701261147.MAA27929@labinfo.iet.unipi.it> From: David Greenman Reply-To: dg@root.com Date: Sun, 26 Jan 1997 04:39:11 -0800 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 ? In the case of NFS, the read should block indefinately. I'm not sure what will happen if the NFS is mounted "soft", however. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project