[lkml]   [2003]   [Jan]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: no version magic, tainting kernel.
On Mon, 27 Jan 2003, Keith Owens wrote:

> Christian Zander <> wrote:
> >The new module
> >is thus built using gcc 3.0, but init/vermagic.o still indicates gcc
> >2.95; the module loader will erroneously believe everything is fine.
> Congratulations, you have put your finger on a major design flaw in
> modversions that has been there since 2.0 kernel days. The modversion
> data is generated once and everything else blindly uses it, with _NO_
> checks on whether it is still valid or not. Rusty knows damn well that
> this is broken, but appears to be ignoring that fact (Rusty, see my
> mail to you and Alan Cox on Wed, 24 Oct 2001 14:14:18 +1000).

First of all, "modversions" has been used to designate the process of
module symbols versioning in the past years, which the above is not. The
version magic string is supposed to be a simple check against obvious
errors like kernel version mismatch between kernel and module and also to
protect against incompatibilities which the ABI checksums (which
modversions is about) cannot detect, like incompatible compiler versions.

As such, the information is known beforehand and now complicated
bookkeeping needed here. (Also, as I just pointed out in a another mail,
the above scenario is not possible).

Now your comments seem to rather apply to the actual module symbol
versioning process, which I just posted a patch for. Things are handled
very much differently now, if you have technical comments on that patch,
they'd be much appreciated.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.090 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site