Date: Fri, 19 Sep 2003 16:36:32 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Marius Strobl <marius@alchemy.franken.de> Cc: w@dream.vg Subject: Re: ATAng still problematic Message-ID: <20030919233632.GB32858@rot13.obsecurity.org> In-Reply-To: <20030919182152.A98528@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>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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? Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/a5MAWry0BWjoQKURAuJjAKDz6APaoXJO3PWLIg2EvdbLubr9NQCgwGx1 3a2cYRfnmy3zSEfH2eNkU9E= =bYUv -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030919233632.GB32858>