> The Oops can happen on any system i can think of when one installs
> serial.o as module, later decides to compile it in and later somehow
> the module gets loaded. One calls rmmod serial and when sombody accesses
> the device, the Oops happens.
>
> The fact is that not a user process explicitely requests overloading the
> module, but kmod itself does it automatically e.g. when setserial is called.
In which case there's a bug in the code which calls kmod, surely? It shouldn't
try to search for a module to handle a device which is already registered.
--
"I don't have any solution but I certainly admire the problem."
- Ashleigh Brilliant
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/