[lkml]   [1997]   [Jan]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: modutils, the next generation
In article <9701141706.AA01204@dcl.MIT.EDU> you wrote:
> Well, a random .o that doesn't have symbol table entries for
> "init_module", "cleanup_module", and "kernel_version", will completely
> fail to be loaded by insmod. So the possibility that insmod will
> accidentally load a random .o into the kernel is pretty much nil.

Yes, but wouldn't it be nice to see whether an object file actually is a
kernel module before you try to insmod it? Of course, you could use nm and
look for the required symbols, but making it obvious from the filename
looks like a good idea to me. Please note that I'm not talking about sanity
checks insmod has to do; all I want is to make it easier for the user to
distinguish between normal object files and objects files that can be
loaded into a kernel.

/* Martin Buck E-Mail: */
/* Student of electrical engineering WWW: */
/* University of Ulm, Germany Snail-Mail: Paukengasse 2, 89077 Ulm, Germany */
#include <disclaimer.h> /* PGP Key available MIME-Mail welcome */

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