Re: [RFC] removal of legacy cdrom drivers (Re: [PATCH] mcdx.c insanity removal)

[viro]

On Mon, May 03, 2004 at 08:08:31PM +0200, Rene Herman wrote:
> viro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
> 
> >OK...  So we have
> >	* potentially faulty mcdx (2.4, apparently either driver corrupts
> >memory in some conditions or isofs does the same for some IO failures -
> >need to take a look at that report more carefully).
> >	* cdu31a (FUBAR driver, nasty to fix, "most of the time" works on
> >2.6)
> >	* sbpcd (at least two, both untested with 2.6)
> 
> 3y25:~$ mount | grep cdrom
> /dev/sbpcd on /mnt/cdrom type iso9660 (ro,noexec,nosuid,nodev)
> 3y25:~$ ls /mnt/cdrom/
> cd.id*        install.exe*  lecdemos/     readme.doc*   resource/ 
> support/
> 
> However, any "cp" from cd-rom oopses the box.

oopses in driver, oopses by triggering BUG() or oopses in fs/*?  The last
two would be more interesting - isofs _MUST_ be able to survive any IO
errors, simply because CDs get scratched, etc. and that shouldn't crash
the box.

> I was actually planning to get around to that at some point. Somewhat 
> fond of this drive. As you say, driver is a disaster area; a few trivial 
> fixes are not what it wants and at this point, fixing it properly would 
> not be a trivial undertaking for me. Am also currently very busy 
> elsewhere. Could it be kept around a bit?

Free advice: if you want to handle that one, fork off the bits you really
need.  Keeping the drivers for all variants together simply doesn't pay,
and even the excuse of keeping the development in single codebase doesn't
apply anymore for what, 7 years?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/