From owner-freebsd-current@FreeBSD.ORG Fri Sep 19 16:36:45 2003 Return-Path: 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 862DF16A4B3 for ; Fri, 19 Sep 2003 16:36:45 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-107-253.dsl.lsan03.pacbell.net [64.169.107.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55FE943FBF for ; Fri, 19 Sep 2003 16:36:44 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id B7D5266D7A; Fri, 19 Sep 2003 16:36:32 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 944F8A88; Fri, 19 Sep 2003 16:36:32 -0700 (PDT) Date: Fri, 19 Sep 2003 16:36:32 -0700 From: Kris Kennaway To: Marius Strobl Message-ID: <20030919233632.GB32858@rot13.obsecurity.org> References: <20030918134850.GA22643@student.agh.edu.pl> <200309181354.h8IDsa0F023908@spider.deepcore.dk> <20030918155125.GC22643@student.agh.edu.pl> <20030919182152.A98528@newtrinity.zeist.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y7xTucakfITjPcLV" Content-Disposition: inline In-Reply-To: <20030919182152.A98528@newtrinity.zeist.de> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: Soren Schmidt 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 23:36:45 -0000 --Y7xTucakfITjPcLV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: > >=20 > > Anyway, here's backtrace for atapicam panic I've mentioned. It's > > triggered by: > >=20 > > cdrecord dev=3D1,1,0 /some/track > >=20 >=20 > 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? Kris --Y7xTucakfITjPcLV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/a5MAWry0BWjoQKURAuJjAKDz6APaoXJO3PWLIg2EvdbLubr9NQCgwGx1 3a2cYRfnmy3zSEfH2eNkU9E= =bYUv -----END PGP SIGNATURE----- --Y7xTucakfITjPcLV--