public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: How can a loadable kernel module remove itself?
Date: Tue, 18 Nov 2003 18:07:49 +0100	[thread overview]
Message-ID: <20031118170748.GF1037@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0311181036590.783-100000@ida.rowland.org>

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

On Tue, 2003-11-18 10:45:57 -0500, Alan Stern <stern@rowland.harvard.edu>
wrote in message <Pine.LNX.4.44L0.0311181036590.783-100000@ida.rowland.org>:
> Say I've got a kernel module that decides its job is done, and it wants to 
> unload itself automatically.  Is there any way to do that?  Basically I'm 
> looking for the opposite of the request_module() function, except that 
> I've already got a pointer to the module in question, i.e., THIS_MODULE.

If the module's runtime is *really* limited (eg. I oftenly use very
small modules to printk() me some bytes from some in-kernel data
structures), then just do what you need to do in the function
"registered" with module_init() and return with != 0...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-11-18 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-18 15:45 How can a loadable kernel module remove itself? Alan Stern
2003-11-18 17:07 ` Jan-Benedict Glaw [this message]

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=20031118170748.GF1037@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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