From: Brian Gerst <bgerst@didntduck.org>
To: Sudharsan Vijayaraghavan <svijayar@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Accessibility of variables between kernel modules
Date: Fri, 21 Feb 2003 16:08:54 -0500 [thread overview]
Message-ID: <3E569566.9080201@didntduck.org> (raw)
In-Reply-To: <4.3.2.7.2.20030222004531.00b56fb0@desh>
Sudharsan Vijayaraghavan wrote:
> Hi,
>
> Am using 2.4 kernel . In this release i find that all non-static symbols
> ( functions/variables) defined in one kernel module are exported by
> default to other kernel modules .
> If we would use EXPORT_NO_SYMBOLS this exporting of symbols is prevented
> . However we can export one of the symbols in one module using
> EXPORT_SYMBOL and then prevent the export of others by immediately
> calling EXPORT_NO_SYMBOLS.
>
> We can even use EXPORT_SYMBOL_GPL to export a symbol from a given module
> , these could be accessed by
> only those modules using MODULE_LICENSE() and are GPL compatible.
>
> However my requirement is quite different. It is as follows.
>
> I have two kernel modules A and B. Is it possible that the variables in
> kernel module A should only be visible to kernel module B and no other
> kernel modules in the system.
> If so please help me out with some explanation.
> Really appreciate your help regarding the same.
>
> Thanks in advance,
> Sudharsan.
Exported symbols are always global. If you want to make sure there are
no symbol conflicts the variable names must be unique. Other than the
GPL symbols, there is no way of preventing other modules from using
exported symbols.
--
Brian Gerst
prev parent reply other threads:[~2003-02-21 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 20:57 Accessibility of variables between kernel modules Sudharsan Vijayaraghavan
2003-02-21 21:08 ` Brian Gerst [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=3E569566.9080201@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=svijayar@cisco.com \
/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