[lkml]   [1997]   [Jan]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: modutils, the next generation
Dale R. Worley ( wrote:

: I think the crux of the matter is that one really does care that only
: proper modules get loaded into the kernel -- the result of loading a
: .o that *wasn't* a module would be ugly indeed.

You cannot insmod an arbitrary .o file. It has to have an init_module
symbol, a cleanup_module symbol, and one of two forms of kernel
version matching information, depending on CONFIG_MODVERSIONS.

: Better would be if
: modules were fully version-locked in some way, so that there was a
: high probability that if a module was incompatible with a particular
: kernel, it would not load at all. And, ideally, if the kernel were
: changed but still compatible with a particular module, the module
: could be loaded unchanged. (Unfortunately, I don't understand the
: module system well enough to know to what degree MODVERSIONS takes
: care of this.)

Well, that's exactly what MODVERSIONS is supposed to take care of.

-- Dave Hinds

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