Re: Oops in register_chrdev, what did I do?

[Arjan van de Ven]

On Mon, Aug 02, 2004 at 12:09:43PM +0200, Måns Rullgård wrote:
> Arjan van de Ven <arjanv@xxxxxxxxxx> writes:
> 
> >> OTOH, wouldn't it be a good idea to refuse loading modules not
> >> matching the running kernel?
> >
> > we do that already... provided you use the kbuild infrastructure instead
> > of a broken self-made makefile hack....
> 
> I used "make -C /lib/modules/`uname -r` SUBDIRS=$PWD modules".  Is
> that not correct?  The breakage was my fault, though.

that is correct

> 
> The problem I see is that a modules contain information about certain
> compiler flags used, e.g. -mregparm, but insmod still attempts to load
> them even they do not match the kernel.  This is independent of what
> build system you used.

that is odd, which modutils is that ? Afaik insmod is supposed to just
refuse (and I've seen it do that as well)

Attachment: pgp00000.pgp
Description: PGP signature