RE: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4, POM-20051227

RE: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4, POM-20051227

[Greg Scott]

Yup, the h323 modules are broken.  The h323 modules reference a function
named ip_conntrack_expect_free.  But searching through the entire kernel
and POM source trees, I find no reference to any files named similarly.
And searching through the netfilter-devel archives from Dec. 2005
through June 2005, I find no mention of this string.  Have I hit a brick
wall or can I remove the references to this function in the effected
h323 modules?  If yes, I will even try my hand at making a patch.

Thanks

- Greg Scott


An extract of the relevant output follows:

[root@dsi-fw linux]# make all
.
.
.
  CC [M]  net/ipv4/netfilter/ip_conntrack_h323_core.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_h323_h225.o
net/ipv4/netfilter/ip_conntrack_h323_h225.c: In function
'h225_parse_connect_uuie':
net/ipv4/netfilter/ip_conntrack_h323_h225.c:135: warning: implicit
declaration of function 'ip_conntrack_expect_free'
  CC [M]  net/ipv4/netfilter/ip_conntrack_h323_h245.o
net/ipv4/netfilter/ip_conntrack_h323_h245.c: In function
'h245_parse_h2250_lchannel_params':
net/ipv4/netfilter/ip_conntrack_h323_h245.c:322: warning: implicit
declaration of function 'ip_conntrack_expect_free'
  CC [M]  net/ipv4/netfilter/asn1_per.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_helper_pptp.o
.
.
.
  LD [M]  net/ipv4/netfilter/ip_conntrack_h323.o
  CC [M]  net/ipv4/netfilter/ip_nat_h323.o
net/ipv4/netfilter/ip_nat_h323.c: In function 'ip_nat_h225':
net/ipv4/netfilter/ip_nat_h323.c:111: warning: implicit declaration of
function 'ip_conntrack_expect_free'
  CC [M]  net/ipv4/netfilter/ip_conntrack_sip.o
  CC [M]  net/ipv4/netfilter/ip_nat_sip.o
net/ipv4/netfilter/ip_nat_sip.c: In function 'ip_nat_sip':
net/ipv4/netfilter/ip_nat_sip.c:97: warning: ISO C90 forbids mixed
declarations and code
  LD [M]  net/ipv4/netfilter/ip_nat.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_netlink.o
.
.
.
  OBJCOPY arch/i386/boot/vmlinux.bin
  HOSTCC  arch/i386/boot/tools/build
  BUILD   arch/i386/boot/bzImage
Root device is (3, 3)
Boot sector 512 bytes.
Setup is 7272 bytes.
System is 1605 kB
Kernel: arch/i386/boot/bzImage is ready  (#2)
  Building modules, stage 2.
  MODPOST
*** Warning: "ip_conntrack_expect_free"
[net/ipv4/netfilter/ip_nat_h323.ko] undefined!
*** Warning: "ip_conntrack_expect_free"
[net/ipv4/netfilter/ip_conntrack_h323.ko] undefined!
  CC      arch/i386/crypto/aes-i586.mod.o
  LD [M]  arch/i386/crypto/aes-i586.ko
.
.
.
[root@dsi-fw linux]# make modules_install
.
.
.
  INSTALL sound/usb/snd-usb-lib.ko
  INSTALL sound/usb/usx2y/snd-usb-usx2y.ko
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F
System.map  2.6.14.5fw20; fi
/bin/sh: line 1:  4266 Killed                  /sbin/depmod -ae -F
System.map 2.6.14.5fw20
make: *** [_modinst_post] Error 137
[root@dsi-fw linux]# date
Thu Dec 29 09:38:37 CST 2005
[root@dsi-fw linux]#

Re: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4, POM-20051227

[Patrick McHardy]

Greg Scott wrote:
> Yup, the h323 modules are broken.  The h323 modules reference a function
> named ip_conntrack_expect_free.  But searching through the entire kernel
> and POM source trees, I find no reference to any files named similarly.
> And searching through the netfilter-devel archives from Dec. 2005
> through June 2005, I find no mention of this string.  Have I hit a brick
> wall or can I remove the references to this function in the effected
> h323 modules?  If yes, I will even try my hand at making a patch.

Expectations are now reference counted, which means you need to
use ip_conntrack_expect_put(). Beware that the semantic has changed,
you need to put every expectation, independant of the success of
ip_conntrack_expect_register(). IIRC the H323 helper has a few other
critical problems, it doesn't set expectfn to NULL in the H.245 helper
(which crashes when the NAT helper is not loaded) and also doesn't
initialize the flags member in the expectation (needs to be 0).

I have a majorly reworked version for some older kernel, it doesn't
compile currently, but I plan to continue working on it in the
near future.

RE: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4, POM-20051227

[Greg Scott]

It looks like the h323 modules are also broken.  I've been watching my
latest kernel build closely this time and ran across the extract below.
This probably explains why the undefined symbols when linking the
kernel.  
.
.
.
  CC [M]  net/ipv4/netfilter/ip_conntrack_proto_udp.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_proto_icmp.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_h323_core.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_h323_h225.o
net/ipv4/netfilter/ip_conntrack_h323_h225.c: In function
'h225_parse_connect_uuie':
net/ipv4/netfilter/ip_conntrack_h323_h225.c:135: warning: implicit
declaration of function 'ip_conntrack_expect_free'
  CC [M]  net/ipv4/netfilter/ip_conntrack_h323_h245.o
net/ipv4/netfilter/ip_conntrack_h323_h245.c: In function
'h245_parse_h2250_lchannel_params':
net/ipv4/netfilter/ip_conntrack_h323_h245.c:322: warning: implicit
declaration of function 'ip_conntrack_expect_free'
  CC [M]  net/ipv4/netfilter/asn1_per.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_helper_pptp.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_proto_gre.o
  CC [M]  net/ipv4/netfilter/ip_nat_core.o
  CC [M]  net/ipv4/netfilter/ip_nat_helper.o
  CC [M]  net/ipv4/netfilter/ip_nat_proto_unknown.o
  CC [M]  net/ipv4/netfilter/ip_nat_proto_tcp.o
  CC [M]  net/ipv4/netfilter/ip_nat_proto_udp.o
  CC [M]  net/ipv4/netfilter/ip_nat_proto_icmp.o
  CC [M]  net/ipv4/netfilter/ip_nat_helper_pptp.o
  CC [M]  net/ipv4/netfilter/ip_nat_proto_gre.o
  CC [M]  net/ipv4/netfilter/ip_nat_rule.o
  CC [M]  net/ipv4/netfilter/ip_nat_standalone.o
  LD [M]  net/ipv4/netfilter/ip_conntrack.o
  LD [M]  net/ipv4/netfilter/ip_conntrack_h323.o
  CC [M]  net/ipv4/netfilter/ip_nat_h323.o
net/ipv4/netfilter/ip_nat_h323.c: In function 'ip_nat_h225':
net/ipv4/netfilter/ip_nat_h323.c:111: warning: implicit declaration of
function 'ip_conntrack_expect_free'
  CC [M]  net/ipv4/netfilter/ip_conntrack_sip.o
  CC [M]  net/ipv4/netfilter/ip_nat_sip.o
net/ipv4/netfilter/ip_nat_sip.c: In function 'ip_nat_sip':
net/ipv4/netfilter/ip_nat_sip.c:97: warning: ISO C90 forbids mixed
declarations and code
  LD [M]  net/ipv4/netfilter/ip_nat.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_netlink.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_proto_sctp.o
  LD [M]  net/ipv4/netfilter/ip_conntrack_pptp.o
  CC [M]  net/ipv4/netfilter/ip_conntrack_amanda.o

.
.
.

- Greg Scott




-----Original Message-----
From: Greg Scott 
Sent: Thursday, December 29, 2005 7:48 AM
To: 'David S. Miller'
Cc: netfilter-devel@lists.netfilter.org
Subject: RE: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4,
POM-20051227


Sorry...I should have checked the archives for references to the tarpit
module.  But that doesn't explain these warnings:

*** Warning: "ip_conntrack_expect_free"
[net/ipv4/netfilter/ip_nat_h323.ko] undefined!
*** Warning: "ip_conntrack_expect_free"
[net/ipv4/netfilter/ip_conntrack_h323.ko] undefined!

The h323 modules were broken before with a missing argument.  I wonder
if they are still broken even after applying Vinay's patch?

I am trying again without the tarpit module.  

- Greg
 

-----Original Message-----
From: David S. Miller [mailto:davem@davemloft.net] 
Sent: Thursday, December 29, 2005 4:30 AM
To: Greg Scott
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4,
POM-20051227


From: "Greg Scott" <GregScott@InfraSupportEtc.com>
Date: Thu, 29 Dec 2005 00:44:02 -0600

> These are only warnings but they make me suspicious.  Should I be
> worried?  Could the warnings below be because something in the kernel 
> calls the modules in question but the modules haven't been built yet? 
> But why would anything in the inline kernel call an optional module 
> loaded from POM?  I've run into several errors getting this far.  I'll

> try a "make mrproper" and then "make all" to build it all from scratch

> now and see what happens.

That tarpit module, as mentioned here by myself in a posting from last
week, is broken and is depending on a symbol that is not exported for a
reason.

To reiterate: It is trying to get the ttl to use in outgoing ipv4 frames
from the sysctl, but that should instead be obtained from the routing
metrics.

RE: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4, POM-20051227

[Greg Scott]

Sorry...I should have checked the archives for references to the tarpit
module.  But that doesn't explain these warnings:

*** Warning: "ip_conntrack_expect_free"
[net/ipv4/netfilter/ip_nat_h323.ko] undefined!
*** Warning: "ip_conntrack_expect_free"
[net/ipv4/netfilter/ip_conntrack_h323.ko] undefined!

The h323 modules were broken before with a missing argument.  I wonder
if they are still broken even after applying Vinay's patch?

I am trying again without the tarpit module.  

- Greg
 

-----Original Message-----
From: David S. Miller [mailto:davem@davemloft.net] 
Sent: Thursday, December 29, 2005 4:30 AM
To: Greg Scott
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4,
POM-20051227


From: "Greg Scott" <GregScott@InfraSupportEtc.com>
Date: Thu, 29 Dec 2005 00:44:02 -0600

> These are only warnings but they make me suspicious.  Should I be 
> worried?  Could the warnings below be because something in the kernel 
> calls the modules in question but the modules haven't been built yet? 
> But why would anything in the inline kernel call an optional module 
> loaded from POM?  I've run into several errors getting this far.  I'll

> try a "make mrproper" and then "make all" to build it all from scratch

> now and see what happens.

That tarpit module, as mentioned here by myself in a posting from last
week, is broken and is depending on a symbol that is not exported for a
reason.

To reiterate: It is trying to get the ttl to use in outgoing ipv4 frames
from the sysctl, but that should instead be obtained from the routing
metrics.

Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4, POM-20051227

[Greg Scott]

These are only warnings but they make me suspicious.  Should I be
worried?  Could the warnings below be because something in the kernel
calls the modules in question but the modules haven't been built yet?
But why would anything in the inline kernel call an optional module
loaded from POM?  I've run into several errors getting this far.  I'll
try a "make mrproper" and then "make all" to build it all from scratch
now and see what happens.  

Thanks

- Greg Scott


Output extract below.  


[root@dsi-fw linux]# make all
  CHK     include/linux/version.h
  SPLIT   include/linux/autoconf.h -> include/config/*
date
  CHK     include/linux/compile.h
  CHK     usr/initramfs_list
  CC [M]  net/ipv4/netfilter/ipt_CONNMARK.o
.
.
.
  OBJCOPY arch/i386/boot/vmlinux.bin
  HOSTCC  arch/i386/boot/tools/build
  BUILD   arch/i386/boot/bzImage
Root device is (3, 3)
Boot sector 512 bytes.
Setup is 7272 bytes.
System is 1605 kB
Kernel: arch/i386/boot/bzImage is ready  (#1)
  Building modules, stage 2.
  MODPOST
*** Warning: "sysctl_ip_default_ttl" [net/ipv4/netfilter/ipt_TARPIT.ko]
undefined!
*** Warning: "ip_conntrack_expect_free"
[net/ipv4/netfilter/ip_nat_h323.ko] undefined!
*** Warning: "ip_conntrack_expect_free"
[net/ipv4/netfilter/ip_conntrack_h323.ko] undefined!
  CC      arch/i386/crypto/aes-i586.mod.o
  LD [M]  arch/i386/crypto/aes-i586.ko
  CC      arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.mod.o
.
.
.
  CC      sound/usb/usx2y/snd-usb-usx2y.mod.o
  LD [M]  sound/usb/usx2y/snd-usb-usx2y.ko
[root@dsi-fw linux]# date
Thu Dec 29 00:14:00 CST 2005
[root@dsi-fw linux]#

Re: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4, POM-20051227

[David S. Miller]

From: "Greg Scott" <GregScott@InfraSupportEtc.com>
Date: Thu, 29 Dec 2005 00:44:02 -0600

> These are only warnings but they make me suspicious.  Should I be
> worried?  Could the warnings below be because something in the kernel
> calls the modules in question but the modules haven't been built yet?
> But why would anything in the inline kernel call an optional module
> loaded from POM?  I've run into several errors getting this far.  I'll
> try a "make mrproper" and then "make all" to build it all from scratch
> now and see what happens.  

That tarpit module, as mentioned here by myself in a posting
from last week, is broken and is depending on a symbol that
is not exported for a reason.

To reiterate: It is trying to get the ttl to use in outgoing
ipv4 frames from the sysctl, but that should instead be obtained
from the routing metrics.