From: Andrew Morton <akpm@osdl.org>
To: Ashutosh Naik <ashutosh.naik@gmail.com>
Cc: anandhkrishnan@yahoo.com, linux-kernel@vger.kernel.org,
rusty@rustcorp.com.au, rth@redhat.com, greg@kroah.com
Subject: Re: [RFC][PATCH] Prevent overriding of Symbols in the Kernel, avoiding Undefined behaviour
Date: Mon, 12 Dec 2005 11:13:22 -0800 [thread overview]
Message-ID: <20051212111322.40be4cfe.akpm@osdl.org> (raw)
In-Reply-To: <81083a450512120439h69ccf938m12301985458ea69f@mail.gmail.com>
Ashutosh Naik <ashutosh.naik@gmail.com> wrote:
>
> When a symbol is exported from the kernel, and say, a module would
> export the same symbol, there currently exists no mechanism to prevent
> the module from exporting this symbol. The module would still go ahead
> and export the symbol, the symbol table would now contain two copies
> of the exported symbol, and hell would break loose.
>
> This patch prevents that from happening, by checking the symbol table
> before relocation for all occurences of the Exported Symbol. If the
> symbol already exists, we branch out with -ENOEXEC. Currently, this
> search is sequential.
Do we really need to do this at runtime? We could check this when building
module depoendencies (for example). That'll be a 95% solution..
next prev parent reply other threads:[~2005-12-12 19:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 12:39 Ashutosh Naik
2005-12-12 12:44 ` Ashutosh Naik
2005-12-12 22:25 ` Jesper Juhl
2005-12-13 8:23 ` Anand H. Krishnan
2005-12-12 19:13 ` Andrew Morton [this message]
2005-12-12 19:27 ` Richard Henderson
2005-12-12 20:20 ` Greg KH
2005-12-12 20:30 ` Jesper Juhl
2005-12-12 22:48 ` Alan Cox
2005-12-13 8:03 ` Arjan van de Ven
2005-12-13 14:32 ` Ashutosh Naik
2005-12-12 22:01 ` Rusty Russell
2005-12-13 14:26 ` Ashutosh Naik
2005-12-13 15:28 ` Ashutosh Naik
2005-12-13 16:49 ` [RFC][PATCH] " Jesper Juhl
2005-12-14 2:03 ` Rusty Russell
2005-12-14 4:10 ` Ashutosh Naik
2005-12-14 5:02 ` Ashutosh Naik
2005-12-15 4:40 ` Andrew Morton
2005-12-15 5:15 ` Rusty Russell
2005-12-15 5:45 ` Ashutosh Naik
2005-12-14 5:46 ` Ashutosh Naik
2005-12-14 23:02 ` Rusty Russell
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=20051212111322.40be4cfe.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=anandhkrishnan@yahoo.com \
--cc=ashutosh.naik@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@redhat.com \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome