From owner-freebsd-current@FreeBSD.ORG  Fri Sep 19 17:17:56 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 20D3316A4BF
	for <freebsd-current@freebsd.org>;
	Fri, 19 Sep 2003 17:17:56 -0700 (PDT)
Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2996E43FF7
	for <freebsd-current@freebsd.org>;
	Fri, 19 Sep 2003 17:17:54 -0700 (PDT)
	(envelope-from marius@newtrinity.zeist.de)
Received: from newtrinity.zeist.de (localhost [127.0.0.1])
	h8K0HQcE069731;	Sat, 20 Sep 2003 02:17:26 +0200 (CEST)
	(envelope-from marius@newtrinity.zeist.de)
Received: (from marius@localhost)
	by newtrinity.zeist.de (8.12.10/8.12.10/Submit) id h8K0HLqa069730;
	Sat, 20 Sep 2003 02:17:21 +0200 (CEST)
	(envelope-from marius)
Date: Sat, 20 Sep 2003 02:17:21 +0200
From: Marius Strobl <marius@alchemy.franken.de>
To: Kris Kennaway <kris@obsecurity.org>
Message-ID: <20030920021721.F52973@newtrinity.zeist.de>
References: <20030918134850.GA22643@student.agh.edu.pl>
	<200309181354.h8IDsa0F023908@spider.deepcore.dk>
	<20030918155125.GC22643@student.agh.edu.pl>
	<20030919182152.A98528@newtrinity.zeist.de>
	<20030919233632.GB32858@rot13.obsecurity.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030919233632.GB32858@rot13.obsecurity.org>;
	from kris@obsecurity.org on Fri, Sep 19, 2003 at 04:36:32PM -0700
cc: freebsd-current@freebsd.org
cc: Soren Schmidt <sos@spider.deepcore.dk>
cc: w@dream.vg
Subject: Re: ATAng still problematic
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Sep 2003 00:17:56 -0000

On Fri, Sep 19, 2003 at 04:36:32PM -0700, Kris Kennaway wrote:
> On Fri, Sep 19, 2003 at 06:21:52PM +0200, Marius Strobl wrote:
> > On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> > > 
> > > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > > triggered by:
> > > 
> > > cdrecord dev=1,1,0 /some/track
> > > 
> > 
> > This panic isn't ATAPICAM related. Could you try the patch below? It's
> > against the cdrtools-devel port but should also work with the cdrtools
> > port.
> 
> Isn't it still a kernel bug if a user process can trigger a panic?
> 

Yes, it seems to be a bug in the mlockall(2) implementation. Backing
it out or hindering cdrecord to use it avoids the panic. I already
wrote an email to bms@ who commited the mlockall(2) and munlockall(2)
support regarding this issue.
The patch for the cdrtools ports is only a workaround until the real
cause is fixed. I also was not sure if it would work for Bryan as I
originally didn't get the same panic as he did.