From owner-freebsd-stable Sun Aug 25 20:37:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A974037B400 for ; Sun, 25 Aug 2002 20:37:48 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA8E443E72 for ; Sun, 25 Aug 2002 20:37:47 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id g7Q3blKD033190; Sun, 25 Aug 2002 21:37:47 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id g7Q3blCj033189; Sun, 25 Aug 2002 21:37:47 -0600 (MDT) (envelope-from ken) Date: Sun, 25 Aug 2002 21:37:47 -0600 From: "Kenneth D. Merry" To: Oliver Fromme Cc: Kal Torak , FreeBSD Stable Subject: Re: tosha port causing system to reboot Message-ID: <20020825213747.B33085@panzer.kdm.org> References: <200208251549.g7PFnbo54349@haluter.fromme.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200208251549.g7PFnbo54349@haluter.fromme.com>; from olli@fromme.com on Sun, Aug 25, 2002 at 05:49:36PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Aug 25, 2002 at 17:49:36 +0200, Oliver Fromme wrote: > > Kal Torak wrote: > > Anyway the problem seems fairly stright forward, I have found that its > > triggerd by reading an audio cd that also contains a data track.. > > I've read a lot of such CD-ROMs without problems. I'm > using a slightly newer version of tosha, however, maybe > that makes a difference. I should finally take the time > to update the port ... :-/ It would be interesting to see if that makes a difference. > > The simple work-around is to just list the tracks you want to extract and > > make sure none of them are data tracks, but in the default mode it tries > > to read the data track as audio and causes the system to panic.. > > > > This just seems like a bug that the program doesnt check the type of track > > before reading it... I will send all the dump and things if its needed, but > > it doesnt seem to be system/hardware related... > > It's certainly system-related. A userland program should > _never_ be able to cause a system panic, no matter if that > program has bugs or not. In this case, I think it is true that tosha should not be able to panic the system. Something is wrong. From the stack trace, it's kinda hard to see any cause and effect, though. In general, though, you can't say that a userland program should never be able to cause a system panic. Using /dev/mem, you can scribble all over the place, including registers on most card in the system. Writing random garbage to /dev/mem will probably panic the system pretty quick. Similarly, anybody with access to a pass device can 'camcontrol format da0'. :) (Not sure whether that would panic the system, since I've never tried it on a boot device. :) It's probably better to say that no *normal* (non-root) user should be able to panic the system, assuming all device permissions are set to their default values. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message