From: Brian Gerst <bgerst@didntduck.org>
To: selvakumar nagendran <kernelselva@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Removing a module even if use count is not zero
Date: Wed, 12 Jan 2005 08:47:51 -0500 [thread overview]
Message-ID: <41E52A87.8080407@didntduck.org> (raw)
In-Reply-To: <20050112085345.88349.qmail@web60607.mail.yahoo.com>
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
next prev parent reply other threads:[~2005-01-12 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 8:53 Removing a module even if use count is not zero selvakumar nagendran
2005-01-12 13:47 ` Brian Gerst [this message]
2005-01-12 15:15 ` Chris Friesen
2005-01-13 4:49 ` exporting /proc entry for module selvakumar nagendran
2005-01-13 4:54 ` Randy.Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41E52A87.8080407@didntduck.org \
--to=bgerst@didntduck.org \
--cc=kernelselva@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox