linux-kernel - Re: 2.6.19-rc3 system freezes when ripping with cdparanoia at ioctl(SG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <454525C1.3070804@ens-lyon.org>
Date:	Sun, 29 Oct 2006 23:05:53 +0100
From:	Brice Goglin <Brice.Goglin@...-lyon.org>
To:	Ken Moffat <zarniwhoop@...world.com>
CC:	Gregor Jasny <gjasny@...glemail.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Jeff Garzik <jgarzik@...ox.com>, linux-ide@...r.kernel.org
Subject: Re: 2.6.19-rc3 system freezes when ripping with cdparanoia at ioctl(SG_IO)

Ken Moffat wrote:
> On Sun, Oct 29, 2006 at 08:20:17PM +0100, Gregor Jasny wrote:
>   
>> Hi,
>>
>> Today I tried the new cdparanoia from Debian Sid (3.10+debian~pre0-2).
>> When I started ripping with "cdparanoia -d /dev/scd0 1" my system
>> freezes after some seconds. There is no oops and even the console
>> cursor stops blinking.
>>
>> If I start cdparanoia with -g /dev/scd0 it starts ripping and but the
>> kernel prints many "program cdparanoia not setting count and/or
>> reply_len properly" warnings. But this seems to be a cdparanoia bug.
>>
>> My CDROM:
>> Vendor:                    PIONEER
>> Product:                   DVD-ROM DVD-106
>> Revision level:            1.22
>>
>>     
>  I'm guessing this is really an IDE drive ?  If so, I suspect the
> problem is in scsi emulation (which doesn't deny that the bug might
> be at least partly in the application, although hanging the box is
> nasty).
>
>  Specifically, I've just compiled that version with the debian patch
> on my (non-debian) amd64 and successfully ripped a CD (without any
> log messages) on both 2.6.18 and 2.6.19-rc3 using /dev/hdc.
>
>  So, if this isn't a real SCSI drive, as a work-around you could try
> disabling ide-scsi and use the IDE device name.
>   

I don't think it is ide-scsi related at all. I would rather think about
libata and/or SATA drivers (I am not sure how to call those IDE drives
that appear as SATA devices...). As shown in the Debian bug report that
Gregor cited[1], the problem has been observed on various machines with
the ata_piix SATA driver (with 2.6.16, .17, .18 and .19-rc kernels).

Brice

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391901

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/