iptables: "getsockopt failed strangely"

Hi,

On PowerPC, with a binary compiled statically, we're seeing
the 
error message in the topic when simply running the iptables
binary.
For more information, the Gentoo bug is available here: 
http://
bugs.gentoo.org/show_bug.cgi?id=136813

Basically, the issue arises from a missing check for the
result from 
the module request located in 
/usr/src/linux/net/ipv4/netfilter/iptables.c

A patch to add a check for -ENOENT and printing out the
missing 
module name then return -EPROTONOSUPPORT instead of -ENOENT
is 
attached and "fixes" the bug for me.

-Joe

Joseph Jezak wrote:
> Hi,
> 
> On PowerPC, with a binary compiled statically, we're
seeing the error
> message in the topic when simply running the iptables
binary.
> For more information, the Gentoo bug is available
here:
> http://
bugs.gentoo.org/show_bug.cgi?id=136813
> 
> Basically, the issue arises from a missing check for
the result from the
> module request located in
/usr/src/linux/net/ipv4/netfilter/iptables.c
> 
> A patch to add a check for -ENOENT and printing out the
missing module
> name then return -EPROTONOSUPPORT instead of -ENOENT is
attached and
> "fixes" the bug for me.


Not sure if I understood the report correctly. It states
iptables
would return -EPROTONOSUPPORT when requesting the version of
a
non-loaded module. Thats not correct since the module will
be
loaded previously by do_ipt_get_ctl.

Its possible though that you use an old iptables version,
we've
had a bug that corrupted errno with some crap before
printing
the error.