From: "Måns Rullgård" <mru@kth.se>
To: arjanv@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in register_chrdev, what did I do?
Date: Mon, 02 Aug 2004 12:09:43 +0200 [thread overview]
Message-ID: <yw1xd629g8bc.fsf@kth.se> (raw)
In-Reply-To: <1091439574.2826.3.camel@laptop.fenrus.com> (Arjan van de Ven's message of "Mon, 02 Aug 2004 11:39:35 +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
next prev parent reply other threads:[~2004-08-02 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 20:01 Oops in register_chrdev, what did I do? Måns Rullgård
2004-08-02 1:09 ` Tommy Reynolds
2004-08-02 8:15 ` Måns Rullgård
2004-08-02 9:36 ` Måns Rullgård
2004-08-02 9:39 ` Arjan van de Ven
2004-08-02 10:09 ` Måns Rullgård [this message]
2004-08-02 10:10 ` Arjan van de Ven
2004-08-02 12:53 ` Måns Rullgård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1xd629g8bc.fsf@kth.se \
--to=mru@kth.se \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.