From: David Ranch <dranch@juniper.net>
To: linux-kernel@vger.kernel.org
Cc: Alan.Cox@linux.org, dranch@trinnet.net
Subject: 2.2.20 - Possible module symbol bug
Date: Fri, 09 Nov 2001 12:48:34 -0800 [thread overview]
Message-ID: <3BEC4122.4C4DFB32@juniper.net> (raw)
Hello esteemed Linux gurus,
I think I've found a bug in 2.2.20. Specifically,
if I compile up a 2.2.20 kernel on a Mandrake 7.0 box
(glibc 2.1.3 - modutil 2.1.121) and run "depmod -a", all
IPMASQ modules, loop, and ide-scsi modules fail dependencies.
--
#depmod -a
/lib/modules/2.2.20/scsi/ide-scsi.o: unresolved symbol(s)
/lib/modules/2.2.20/block/loop.o: unresolved symbol(s)
/lib/modules/2.2.20/ipv4/ip_masq_vdolive.o: unresolved symbol(s)
/lib/modules/2.2.20/ipv4/ip_masq_quake.o: unresolved symbol(s)
/lib/modules/2.2.20/ipv4/ip_masq_raudio.o: unresolved symbol(s)
/lib/modules/2.2.20/ipv4/ip_masq_irc.o: unresolved symbol(s)
/lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol(s)
/lib/modules/2.2.20/ipv4/ip_masq_user.o: unresolved symbol(s)
#modprobe --debug ip_masq_ftp
/lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_new
/lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_put
/lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_listen
/lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_control_add
/lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_out_get
--
If I do this make config on a a Mandrake 7.2 machine
(Glibc 2.1.3 - modutils 2.3.21), only the loop module fails.
If I do this on a Mandrake 8.0 machine (Glibc 2.2.2 - modutils 2.4.3),
everything is FINE.
So, playing around with the kernel config a little, I've found
that if I -do not- enable "CONFIG_MODVERSIONS", then everything
is ok on all machines.
Any thoughts on what is going on? If possible, please CC: on the
the reply as I'm not on the linux-kernel list nor can my email
box handle the additional load. ;-) Thanks.
Ps. If anyone would like a copy of the .config or the System.map
files, please email me.
--David
next reply other threads:[~2001-11-09 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-09 20:48 David Ranch [this message]
2001-11-10 6:28 ` 2.2.20 - Possible module symbol bug Keith Owens
[not found] ` <Your message of "Fri, 09 Nov 2001 12:48:34 -0800." <3BEC4122.4C4DFB32@juniper.net>
2001-11-11 4:38 ` David Ranch
2001-11-11 6:03 ` Keith Owens
2001-11-13 21:17 ` Eric Preston
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=3BEC4122.4C4DFB32@juniper.net \
--to=dranch@juniper.net \
--cc=Alan.Cox@linux.org \
--cc=dranch@trinnet.net \
--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