public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Brian Gerst <bgerst@didntduck.org>
Cc: forop066@zaz.com.br, linux-kernel@vger.kernel.org
Subject: Re: Calling module symbols from inside the kernel !
Date: Tue, 07 Nov 2000 14:41:42 +0000	[thread overview]
Message-ID: <13979.973608102@redhat.com> (raw)
In-Reply-To: <3A070BEF.7712DEDB@didntduck.org>
In-Reply-To: <3A070BEF.7712DEDB@didntduck.org>  <200011061924.QAA31314@srv1-for.for.zaz.com.br>


bgerst@didntduck.org said:
>  You will need to use a function pointer hook that the module fills in
> when it is loaded.  For an example look at devpts_upcall_new and
> devpts_upcall_kill in fs/devpts/inode.c.  The hooks are resident in
> the kernel and are exported so the module can see them.  The caller
> then needs to check if the hook is null and optionally request the
> module be loaded.

get_module_symbol() does this for you without having to use such a hook

/me runs


:)


--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-07 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-06 19:24 Calling module symbols from inside the kernel ! forop066
2000-11-06 19:52 ` Brian Gerst
2000-11-07  3:11 ` Keith Owens
2000-11-07 14:41 ` David Woodhouse [this message]
2000-11-08 11:52   ` Ingo Oeser
  -- strict thread matches above, loose matches on Subject: below --
2000-11-07  7:52 richardj_moore

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=13979.973608102@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=bgerst@didntduck.org \
    --cc=forop066@zaz.com.br \
    --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