Date: Sun, 26 Jan 1997 04:01:01 -0800 From: David Greenman <dg@root.com> To: Steven Wallace <swallace@ece.uci.edu> Cc: current@FreeBSD.org Subject: Re: exec bug Message-ID: <199701261201.EAA06656@root.com> In-Reply-To: Your message of "Sun, 26 Jan 1997 00:35:21 PST." <199701260835.AAA05470@newport.ece.uci.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>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? There is no good solution to this problem given the current architecture. I don't consider it a significant problem, however. People can crash your system (due to intentional consistency checks) just as easily by putting in a floppy with a corrupted filesystem. The only solution I can think of at the moment to this problem would be to change the code to do a read of the file header into a malloced buffer. The overhead for this would be very (unacceptably) high, however. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701261201.EAA06656>