netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Salatiel Filho <salatiel.filho@gmail.com>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: iptables -> can't initialize iptables table `filter': Bad file descriptor
Date: Tue, 04 Dec 2007 16:07:30 +0100	[thread overview]
Message-ID: <47556D32.1060901@trash.net> (raw)
In-Reply-To: <beb91d720712040645w76be238bmdd9dc362bf601755@mail.gmail.com>

[netfilter-devel re-added. Please don't drop CCs]

Salatiel Filho wrote:
> On 12/4/07, Patrick McHardy <kaber@trash.net> wrote:
>
>>> I tried the patch but it didn`t work.
>>>
>>> ~# iptables --version [patched now]
>>> iptables v1.3.8
>>>
>>> ~# iptables -L
>>> iptables v1.3.8: can't initialize iptables table `filter': Invalid argument
>>> Perhaps iptables or your kernel needs to be upgraded.
>>
>> Could you send another strace please?
>>

> getsockopt(3, SOL_IP, 0x40 /* IP_??? */,
> "filter\0\0\0\0\0\0\340?\3@\310[\1@\1\0\0\0\244\213\0\0"..., [84]) = 0
> brk(0)                                  = 0x1c000
> brk(0x3d000)                            = 0x3d000
> getsockopt(3, SOL_IP, 0x41 /* IP_??? */, 0x1c0c0, 0xbea55c24) = -1


Thanks. The invalid fd usage is gone, this seems to be a problem
in the interaction between kernel and userspace. Please enable
debugging as I wrote a couple of mails ago and post the output.

  parent reply	other threads:[~2007-12-04 15:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02 19:22 iptables -> can't initialize iptables table `filter': Bad file descriptor Salatiel Filho
2007-12-03  8:07 ` Patrick McHardy
2007-12-03 12:35   ` Salatiel Filho
2007-12-04  8:18     ` Patrick McHardy
2007-12-04  8:51       ` Jan Engelhardt
2007-12-04  8:58         ` Jesper Dangaard Brouer
2007-12-04  9:14         ` Patrick McHardy
2007-12-04 14:16           ` Salatiel Filho
2007-12-04 14:18             ` Patrick McHardy
     [not found]               ` <beb91d720712040645w76be238bmdd9dc362bf601755@mail.gmail.com>
2007-12-04 15:07                 ` Patrick McHardy [this message]
2007-12-04 15:40                   ` Salatiel Filho
2007-12-04 15:57                     ` Patrick McHardy
2007-12-04 16:05                       ` Salatiel Filho
2007-12-04 16:15                         ` Patrick McHardy
2007-12-04 16:32                           ` Salatiel Filho
2007-12-05  8:05                             ` Patrick McHardy
2007-12-05 11:39                               ` Salatiel Filho
2007-12-06  9:51                                 ` Patrick McHardy
2007-12-06 11:25                                   ` Salatiel Filho
2007-12-09 13:34                                     ` Salatiel Filho
2007-12-09 14:11                                       ` Salatiel Filho
2007-12-11 10:29                                         ` Patrick McHardy
2007-12-13 21:41                                           ` Laurence J. Lane
2007-12-13 22:14                                             ` Salatiel Filho
2007-12-14  9:22                                               ` Patrick McHardy
2007-12-14 12:39                                                 ` Salatiel Filho

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=47556D32.1060901@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=salatiel.filho@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).