[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: unable to rmmod
On Wednesday 05 November 2008 12:43:06 Manish Katiyar wrote:
> On Wed, Nov 5, 2008 at 4:23 PM, nidhi mittal <nidhimittal19@xxxxxxxxx> wrote:
> > Hi
> > i m facing this prob from long that when i use a module which i have just
> > inserted.
> > now suppose by mistake some kernel oops occur null pointer exception lets
> > say ..
> > now my program which was using the function of module is closed .
> > so in my knowledge no one is using my module now.
> >
> > now i corrected the mistake in module re compiled it and tried to rmmod
> > previous version of module.
> > but error came as module is in use cannot rmmod....
> >
> > i tried to rmmod by force too but its not working ...
>
> I think you should do select the following in your kernel config
>
> Enable loadable module support --->
> [ ] Forced module loading (NEW)
> [*] Module unloading
> [ ] Forced module unloading
or the forced unloading switch.
Anyhow, rmmod will not remove a module in use, rmmod -w will wait untill it can
be removed (which, unfortunately will not happen in your case).
Finally, you have rmmod -f (which requires CONFIG_MODULE_FORCE_UNLOAD
during the build, hence 'Forced module unloading').
Do note that forcing out a module can be quite hazardous.. :-)
--
Henrik
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ