Messages in this thread | | | Subject | Re: Oops in register_chrdev, what did I do? | From | Måns Rullgård <> | Date | Mon, 02 Aug 2004 12:09:43 +0200 |
| |
Arjan van de Ven <arjanv@redhat.com> 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.
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.
-- Måns Rullgård mru@kth.se - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |