From: Keith Owens <kaos@ocs.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: chris@chrullrich.de (Christian Ullrich), linux-kernel@vger.kernel.org
Subject: Re: insmod problem after modutils upgrading
Date: Thu, 14 Dec 2000 09:05:13 +1100 [thread overview]
Message-ID: <4381.976745113@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 13 Dec 2000 21:10:54 -0000." <E146JAu-0003HX-00@the-village.bc.nu>
On Wed, 13 Dec 2000 21:10:54 +0000 (GMT),
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>It is modutils. Their behaviour changed in a non back compatible way. Do not
>use modutils 2.3.22 with Linux 2.2.* is the simple answer. Perhaps Keith can
>make this a warning in 2.3.23
Adding persistent module data to modutils meant that insmod had to be a
lot more picky about MODULE_PARM() entries. There were a few modules
that had invalid MODULE_PARM() entries, nobody had spotted them
previously because nobody used those options. Since these are bugs in
the modules and only a few modules are affected (less than 5 reported),
the fix is to correct the modules that have coding errors.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-13 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 17:41 insmod problem after modutils upgrading Corisen
2000-12-13 20:59 ` Christian Ullrich
2000-12-13 21:04 ` Jeff Garzik
2000-12-13 21:10 ` Alan Cox
2000-12-13 21:11 ` Jeff Garzik
2000-12-13 22:05 ` Keith Owens [this message]
2000-12-13 22:13 ` Alan Cox
2000-12-14 0:02 ` Keith Owens
2000-12-14 0:43 ` Alan Cox
2000-12-14 12:32 ` Horst von Brand
2000-12-14 17:50 ` Alan Cox
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=4381.976745113@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@chrullrich.de \
--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.