From owner-freebsd-current@FreeBSD.ORG  Fri Sep 19 18:15:17 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 B167D16A4B3
	for <freebsd-current@freebsd.org>;
	Fri, 19 Sep 2003 18:15:17 -0700 (PDT)
Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7280D43FCB
	for <freebsd-current@freebsd.org>;
	Fri, 19 Sep 2003 18:15:16 -0700 (PDT)
	(envelope-from marius@newtrinity.zeist.de)
Received: from newtrinity.zeist.de (localhost [127.0.0.1])
	h8K1EncE072016;	Sat, 20 Sep 2003 03:14:49 +0200 (CEST)
	(envelope-from marius@newtrinity.zeist.de)
Received: (from marius@localhost)
	by newtrinity.zeist.de (8.12.10/8.12.10/Submit) id h8K1EifW072015;
	Sat, 20 Sep 2003 03:14:44 +0200 (CEST)
	(envelope-from marius)
Date: Sat, 20 Sep 2003 03:14:44 +0200
From: Marius Strobl <marius@alchemy.franken.de>
To: Bruce M Simpson <bms@spc.org>
Message-ID: <20030920031443.G52973@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> <20030920021721.
	<20030920021721.F52973@newtrinity.zeist.de>
	<20030920004744.GA13242@saboteur.dek.spc.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: <20030920004744.GA13242@saboteur.dek.spc.org>;
	from bms@spc.org on Sat, Sep 20, 2003 at 01:47:44AM +0100
cc: w@dream.vg
cc: freebsd-current@freebsd.org
cc: Soren Schmidt <sos@spider.deepcore.dk>
cc: Kris Kennaway <kris@obsecurity.org>
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 01:15:17 -0000

On Sat, Sep 20, 2003 at 01:47:44AM +0100, Bruce M Simpson wrote:
> On Sat, Sep 20, 2003 at 02:17:21AM +0200, Marius Strobl wrote:
> > > 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.
> 
> I don't think that's been conclusively established yet, so statements
> of the form above are a bit unhelpful.
> 

Ok, sorry.

> The problem may well lie elsewhere in the system, as a parameter in
> vm_map_copy_entry() is being unexpectedly set to NULL in the backtrace
> which you provided me with.
> 

It's just certainly not ATAng or ATAPICAM as I get this panic on a
SCSI-only box, too.

> If more people can exercise the same codepath as you appear to be
> exercising with different configurations, then I will have more to go on.
>