From: "Salatiel Filho" <salatiel.filho@gmail.com>
To: "Patrick McHardy" <kaber@trash.net>
Cc: "Laurence J. Lane" <ljlane@debian.org>,
"Netfilter Development Mailinglist"
<netfilter-devel@vger.kernel.org>
Subject: Re: iptables -> can't initialize iptables table `filter': Bad file descriptor
Date: Fri, 14 Dec 2007 09:39:38 -0300 [thread overview]
Message-ID: <beb91d720712140439i13c730d9o687bfc22d3e58add@mail.gmail.com> (raw)
In-Reply-To: <47624B66.5060205@trash.net>
On Dec 14, 2007 6:22 AM, Patrick McHardy <kaber@trash.net> wrote:
> Salatiel Filho wrote:
> > On 12/13/07, Laurence J. Lane <ljlane@debian.org> wrote:
> >> On Dec 11, 2007 5:29 AM, Patrick McHardy <kaber@trash.net> wrote:
> >>
> >>> It shouldn't, but I haven't seen any other complaints about this
> >>> yet, so please try to either compile the kernel natively or also
> >>> cross-compile iptables.
> >> [ I'm jumping in on the end of the thread with comments not directed
> >> at anyone specific.]
> >>
> >> I just saw an additional comment to #446685. A search for "EABI iptables"
> >> shows a known arm iptables' problem and at least one workaround is the chroot
> >> method mentioned in the report.
> >>
> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446685
>
>
> The bad fd bug visible in the strace attached to that report is the
> one I fixed in SVN.
>
> > I have not test the solution cause i have to download 116MB to chroot :)
> > But i`m curious , if i compile both source kernel and source iptables
> > , should`t they be compatible ?
>
>
> They should, unless something is causing different structure layout.
>
I tried chroot in that rootfs. But when i try to run iptables i get
# iptables -L
ERROR: 0 not a valid target)
Aborted
So that is not a workaround.
--
[]'s
Salatiel
"O maior prazer do inteligente é bancar o idiota
diante de um idiota que banca o inteligente".
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-12-14 12:39 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
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 [this message]
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=beb91d720712140439i13c730d9o687bfc22d3e58add@mail.gmail.com \
--to=salatiel.filho@gmail.com \
--cc=kaber@trash.net \
--cc=ljlane@debian.org \
--cc=netfilter-devel@vger.kernel.org \
/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).