From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Ashutosh Naik <ashutosh.naik@gmail.com>,
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 22:48:32 +0000 [thread overview]
Message-ID: <1134427712.10304.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20051212111322.40be4cfe.akpm@osdl.org>
On Llu, 2005-12-12 at 11:13 -0800, Andrew Morton wrote:
> 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..
Its almost the 0% solution. The kernel as shipped doesn't seem to have
any clashing symbols like this. The two sets of cases people report are
1. Out of tree modules
2. Reconfiguring, rebuilding something from kernel to module and not
cleaning up
A dep time solution might fix one of those but robustness here would be
good, especially as once the installation is incorrect end users can
often trigger hotplug loads that cause problems.
next prev parent reply other threads:[~2005-12-12 22:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 12:39 [RFC][PATCH] Prevent overriding of Symbols in the Kernel, avoiding Undefined behaviour 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
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 [this message]
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=1134427712.10304.6.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=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