David Stroupe wrote: > I have written a driver for a data acqusition board. That having been > completed, I am adding supporting user space code in the form of C++ > classes and such. During this development, I find errors in my user > space code that causes a crash (null pointer and such). When this > happens, the driver is still running fine, but sometimes claims that it > can not be removed because it still thinks that the crashed app is using > it. (I assume that the driver is still ok because I can start a new > application and talk to the driver and board) What is the appropriate > way to resolve this issue at the driver level? I don't have any > specific "uses counter" in my driver that is being incremented, so > how/why does the driver think that it is busy? What about INC_MOD_COUNT and DEC_MOD_COUNT? A mis-match of those would keep you from unloading... HTH, Eli --------------------. "If it ain't broke now, Eli Carter \ it will be soon." -- crypto-gram eli.carter(a)inet.com `------------------------------------------------- -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
