From: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: bugme-daemon@kernel-bugs.osdl.org
Subject: [Bugme-new] [Bug 8957] New: Exported functions and variables
Date: Thu, 30 Aug 2007 09:41:41 -0700 (PDT) [thread overview]
Message-ID: <910709.35108.qm@web52002.mail.re2.yahoo.com> (raw)
I thought that the bug might happen when two kernel modules are being loaded. If module A is loaded and its code includes references to functions exported by module B, I thought module A could call those functions before the module_init function of module B has finished. I was not thinking about buggy calls to registering interface functions. I just thought that the kernel should not allow symbols exported by EXPORT_SYMBOLto be visible to other modules before the module_init function is finished. One could code the exported functions so that they could be safely called by anyone while the module_init function is being called but that would be an unnecessary burden for coders. I think that a module should expose its functions and variables only by calling registering interface functions before the module_init function is finished. So I think the design of the kernel modules is flawed if it allows anyone to call exported functions before the module_init
function is finished.
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit dem neuen Yahoo! Mail. www.yahoo.de/mail
next reply other threads:[~2007-08-30 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 16:41 Matti Linnanvuori [this message]
2007-08-30 16:56 ` [Bugme-new] [Bug 8957] New: Exported functions and variables Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2007-08-30 17:44 Matti Linnanvuori
2007-08-31 16:06 ` Satyam Sharma
2007-08-31 17:14 Matti Linnanvuori
2007-08-31 17:28 ` Arjan van de Ven
2007-08-31 23:49 ` Satyam Sharma
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=910709.35108.qm@web52002.mail.re2.yahoo.com \
--to=mattilinnanvuori@yahoo.com \
--cc=bugme-daemon@kernel-bugs.osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.