From: selvakumar nagendran <kernelselva@yahoo.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: exporting /proc entry for module
Date: Wed, 12 Jan 2005 20:49:12 -0800 (PST) [thread overview]
Message-ID: <20050113044912.40078.qmail@web60610.mail.yahoo.com> (raw)
In-Reply-To: <41E53F27.9000502@nortelnetworks.com>
--- 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
next prev parent reply other threads:[~2005-01-13 4:49 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
2005-01-12 15:15 ` Chris Friesen
2005-01-13 4:49 ` selvakumar nagendran [this message]
2005-01-13 4:54 ` exporting /proc entry for module 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=20050113044912.40078.qmail@web60610.mail.yahoo.com \
--to=kernelselva@yahoo.com \
--cc=cfriesen@nortelnetworks.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
Powered by JetHome