From: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: bugme-daemon@kernel-bugs.osdl.org
Subject: [Bugme-new] [Bug 8957] New: Exported functions and variables
Date: Fri, 31 Aug 2007 10:14:27 -0700 (PDT) [thread overview]
Message-ID: <116718.45429.qm@web52005.mail.re2.yahoo.com> (raw)
It seems to me that kernel/module.c allows the whole kernel to use exported symbols during the execution of the init function if they are weak:
/* Ok if weak. */
if (ELF_ST_BIND(sym[i].st_info) == STB_WEAK)
break;
That seems a possible way to produce the scenario of this so-called bug.
________
Yahoo! Clever: Stellen Sie Fragen und finden Sie Antworten. Teilen Sie Ihr Wissen. www.yahoo.de/clever
next reply other threads:[~2007-08-31 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 17:14 Matti Linnanvuori [this message]
2007-08-31 17:28 ` [Bugme-new] [Bug 8957] New: Exported functions and variables Arjan van de Ven
2007-08-31 23:49 ` Satyam Sharma
-- 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-30 16:41 Matti Linnanvuori
2007-08-30 16:56 ` Arjan van de Ven
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=116718.45429.qm@web52005.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox