From: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
To: Keith Owens <kaos@ocs.com.au>
Cc: Alan.Cox@linux.org, linux-kernel@vger.kernel.org
Subject: Re: Checking for incorrect MODULE_PARM
Date: Sun, 10 Dec 2000 13:38:56 -0300 [thread overview]
Message-ID: <200012101638.eBAGcuJ16062@sleipnir.valparaiso.cl> (raw)
In-Reply-To: Your message of "Sun, 10 Dec 2000 23:06:10 +1100." <18434.976449970@ocs3.ocs-net>
Keith Owens <kaos@ocs.com.au> said:
> modutils 2.3.22 does more rigorous checking of MODULE_PARM entries and
> has already found several cases where MODULE_PARM(x) is used but the
> corresponding variable 'x' is not defined. These are module coding
> bugs that were previously hidden. Run this script to do a quick check
> of all your modules against modutils 2.3.22. Run as any user, does not
> have not be root.
>
> for i in $(/sbin/modprobe -l)
> do
> (echo -e "\n" $i ; /sbin/modinfo -p $i) > /var/tmp/modinfo
> grep warning /var/tmp/modinfo > /dev/null && cat /var/tmp/modinfo
> done
With 2.2.18pre27 on i686 I get:
/lib/modules/2.2.18/ipv4/ip_masq_user.o
warning: symbol for parameter ports not found
ports int array (min = 1, max = 12)
debug int
Hope this helps a bit.
--
Horst von Brand vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Vin~a del Mar, Chile +56 32 672616
-
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-10 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-10 12:06 Keith Owens
2000-12-10 16:38 ` Horst von Brand [this message]
2000-12-10 23:58 ` Keith Owens
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=200012101638.eBAGcuJ16062@sleipnir.valparaiso.cl \
--to=vonbrand@sleipnir.valparaiso.cl \
--cc=Alan.Cox@linux.org \
--cc=kaos@ocs.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®