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: Jan Engelhardt <jengelh@computergmbh.de>,
	netfilter-devel@vger.kernel.org,
	Jesper Dangaard Brouer <hawk@diku.dk>
Subject: Re: iptables -> can't initialize iptables table `filter': Bad file descriptor
Date: Tue, 04 Dec 2007 15:18:46 +0100	[thread overview]
Message-ID: <475561C6.4030704@trash.net> (raw)
In-Reply-To: <beb91d720712040616o7e2ac99ch51ade98dbbd2efa@mail.gmail.com>

Salatiel Filho wrote:
> On 12/4/07, Patrick McHardy <kaber@trash.net> wrote:
>
>> Salatiel, does this patch fix the problem?
>>
>> Index: libiptc/libiptc.c
>> ===================================================================
>> --- libiptc/libiptc.c   (Revision 7130)
>> +++ libiptc/libiptc.c   (Arbeitskopie)
>> @@ -866,10 +866,6 @@
>>         CHECK(h);
>>         return h;
>>  error:
>> -       if (--sockfd_use == 0) {
>> -               close(sockfd);
>> -               sockfd = -1;
>> -       }
>>         TC_FREE(&h);
>>         return NULL;
>>  }
>>
>>
> 
> 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?

  reply	other threads:[~2007-12-04 14:18 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 [this message]
     [not found]               ` <beb91d720712040645w76be238bmdd9dc362bf601755@mail.gmail.com>
2007-12-04 15:07                 ` Patrick McHardy
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=475561C6.4030704@trash.net \
    --to=kaber@trash.net \
    --cc=hawk@diku.dk \
    --cc=jengelh@computergmbh.de \
    --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).