Re: Something broke cdu31a driver between 2.0.33 and .33

Erik Andersen (andersen@inconnect.com)
Wed, 3 Jun 1998 18:00:57 -0600 (MDT)


On Wed, 3 Jun 1998, Yann Dirson wrote:

[---------------snip-------------------]
>
> Note that I also found out it was possible to rmmod the cdu31a module
> before cdplay has exited (ie, when it is looping), and that causes a
> kernel OOPS, as well as cdplay segfaulting.
>
> --
> Yann Dirson <ydirson@a2points.com>

Are you sure you saw this in 2.0.x? I know this is currently possible under
2.1.x (this Oops is actually possible in all cdrom drivers using the Uniform
cdrom driver -- scsi and ide-cd included) and I must and _will_ fix this
before 2.2.0 is released. I already know what to do, but I just havn't
fixed it yet. I just need to add in a pre-ioctl and post-ioctl callback
to the low-level drivers so they can inc/dec the module use count. This will
also elegantly fix another problem with cdu31a -- the fact that we need to
ensure the drive is spun up before doing stuff. The way that is currently
done for cdu31a and sbpcd is an ugly hack.

I wasn't aware that the 2.0.x version of cdu31a (which doesn't use the
uniform cdrom driver) also had this problem (but then I havn't run 2.0.x
for about a year and I don't have one of these drives...). Could you
confirm the kernel version number for this part of your report?

-Erik

--
Erik B. Andersen   Web:    http://www.inconnect.com/~andersen/ 
                   email:  andersee@debian.org
--This message was written using 73% post-consumer electrons--

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu