Removing a module even if use count is not zero

Removing a module even if use count is not zero

[selvakumar nagendran]

hello linux-experts,
    I inserted my module into the running kernel that
intercepts read system call. I am using kernel 2.4.28.
Now, I am unable to remove it since each and every
time, the module is used by some process. How can I
remove the module even if the usecount is not zero?
    Can anyone help me regarding this?

Thanks,
selva


		
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 

Re: Removing a module even if use count is not zero

[Brian Gerst]

selvakumar nagendran wrote:
> hello linux-experts,
>     I inserted my module into the running kernel that
> intercepts read system call. I am using kernel 2.4.28.
> Now, I am unable to remove it since each and every
> time, the module is used by some process. How can I
> remove the module even if the usecount is not zero?
>     Can anyone help me regarding this?
> 
> Thanks,
> selva
> 

Reboot.  If you remove it, the system will likely crash.

--
				Brian Gerst

Re: Removing a module even if use count is not zero

[Chris Friesen]

selvakumar nagendran wrote:
> hello linux-experts,
>     I inserted my module into the running kernel that
> intercepts read system call. I am using kernel 2.4.28.
> Now, I am unable to remove it since each and every
> time, the module is used by some process. How can I
> remove the module even if the usecount is not zero?
>     Can anyone help me regarding this?

As already said, you need to reboot.

To fix this in the future, export a /proc entry that when written to 
causes your module to properly clean everything up and prevent anyone 
from getting new accesses.  This then allows you to remove the module 
cleanly.  Note that it may not be possible to cleanly deregister, 
depending on what your module is doing.

Chris

exporting /proc entry for module

[selvakumar nagendran]

--- Chris Friesen <cfriesen@nortelnetworks.com> wrote:
> To fix this in the future, export a /proc entry that
> when written to 
> causes your module to properly clean everything up
> and prevent anyone 
> from getting new accesses.  This then allows you to
> remove the module 
> cleanly.  Note that it may not be possible to
> cleanly deregister, 
> depending on what your module is doing.
> 
> Chris

  How can I export a /proc entry for my module?

Regards,
selva


		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 

Re: exporting /proc entry for module

[Randy.Dunlap]

selvakumar nagendran wrote:
> --- Chris Friesen <cfriesen@nortelnetworks.com> wrote:
> 
>>To fix this in the future, export a /proc entry that
>>when written to 
>>causes your module to properly clean everything up
>>and prevent anyone 
>>from getting new accesses.  This then allows you to
>>remove the module 
>>cleanly.  Note that it may not be possible to
>>cleanly deregister, 
>>depending on what your module is doing.
>>
> 
>   How can I export a /proc entry for my module?

. . . . . . . . . .

You can study the valuable documents at
http://kernelnewbies.org/documents/

or google for other procfs example source code,
which should find several examples for you,
such as http://www.xenotime.net/linux/procfs_ex/

-- 
~Randy