From owner-freebsd-current  Sun Jan 26 00:35:29 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA26839
          for current-outgoing; Sun, 26 Jan 1997 00:35:29 -0800 (PST)
Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA26834
          for <current@freebsd.org>; Sun, 26 Jan 1997 00:35:27 -0800 (PST)
Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.8.5) id AAA29574; Sun, 26 Jan 1997 00:35:24 -0800 (PST)
Received: from localhost by newport.ece.uci.edu (8.8.5) id AAA05470; Sun, 26 Jan 1997 00:35:22 -0800 (PST)
Message-Id: <199701260835.AAA05470@newport.ece.uci.edu>
To: current@freebsd.org
Subject: exec bug
Date: Sun, 26 Jan 1997 00:35:21 -0800
From: Steven Wallace <swallace@ece.uci.edu>
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.

This is in 2_2_RELENG.

I'd hate to have anyone be able to panic my system by putting in
a bad floppy or CDROM and trying to execute something.

What's the deal?

Thanks, Steven