Re: 2.2.20 - Possible module symbol bug

[Eric Preston]

> #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 

I noticed the same problem when recently building 2.2.20,

Enable "prompt for experimental code"
And choose the appropriate masq options that now appear,
and the masq stuff goes away. Something to do with CONFIG_MASQUERADE_MOD
not being set, was in a hurry so i didn't bother to look into it more,

regards,
Eric