linux-kernel - Re: [regression] CD-DA delay needed after insertion (http://bugzilla.kernel.org/show

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: <Pine.LNX.4.64.0809301719000.5818@vixen.sonytel.be>
Date:	Tue, 30 Sep 2008 17:21:29 +0200 (CEST)
From:	Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>
To:	Monty Montgomery <monty@...h.org>
cc:	James Bottomley <James.Bottomley@...senpartnership.com>,
	linux-scsi@...r.kernel.org,
	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: [regression] CD-DA delay needed after insertion
 (http://bugzilla.kernel.org/show_bug.cgi?id=10974)

On Tue, 30 Sep 2008, Monty Montgomery wrote:
> > With latest cdparanoia git-^H^H^H^Hsvn, the problem still happens.
> > After applying the patch below, there's no more crash thanks to your last
> > commit, and It Just Works(tm):
> 
> Then I will be doing some headscratching over a copy of the kernel.
> Oh--  what *exact* kernel are you using?  non-x86 trees don't always
> sync often with the 'official' mainline and I want to be sure I'm
> reading the correct thing.  I was a longtime PPC user until about two
> years ago, and I'm used to there being several substantially different
> PPC kernel trees [just making sure].

It happens on anything after 2.6.24 (cfr.
http://bugzilla.kernel.org/show_bug.cgi?id=10974).
E.g. mainline 2.6.27-rc8.

> OTOH, if the kernel isn't even servicing the device as a block device
> until the drive returns a ready status and O_NONBLOCK thwarts waiting
> for that.... sigh.  Nothing like a passthrough interface that still
> isn't a passthrough interface after fifteen years of dicking around.
> 
> I'm not willing to cripple cdparanoia on more-than-one-cdrom systems
> because of an edge case due to yet another ill-considered block layer
> 'feature'.  For one thing *I* need to be able to scan devices without
> blocking on my own multiple drive systems.  If there's a workaround to
> get both, I will find it.
> 
> But it's too early to say for sure.  I'll check again.

The difficult part is who's to blame: Linux commit
38582a62ecd337de4212004c7d4844899dc57890 or cdparanoia?

> (May I ask-- why the hard starting/stopping of the interface?  Power saving?]

Which hard starting/stopping do you mean?

Thanks!

With kind regards,

Geert Uytterhoeven
Software Architect

Sony Techsoft Centre Europe
The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium

Phone:    +32 (0)2 700 8453
Fax:      +32 (0)2 700 8622
E-mail:   Geert.Uytterhoeven@...ycom.com
Internet: http://www.sony-europe.com/

A division of Sony Europe (Belgium) N.V.
VAT BE 0413.825.160 · RPR Brussels
Fortis · BIC GEBABEBB · IBAN BE41293037680010