From: "David S. Miller" <davem@davemloft.net>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@oss.sgi.com, dtor_core@ameritech.net,
netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: Last night Linus bk - netfilter busted?
Date: Fri, 11 Mar 2005 10:51:36 -0800 [thread overview]
Message-ID: <20050311105136.2a5e4ddc.davem@davemloft.net> (raw)
In-Reply-To: <4231A498.4020101@trash.net>
On Fri, 11 Mar 2005 15:00:56 +0100
Patrick McHardy <kaber@trash.net> wrote:
> Works fine here. You could try if reverting one of these two patches
> helps (second one only if its a SMP box).
>
> ChangeSet@1.2010, 2005-03-09 20:28:17-08:00, bdschuym@pandora.be
> [NETFILTER]: Reduce call chain length in netfilter (take 2)
It's this change, I know it is, because Linus sees the same problem
on his workstation.
You wouldn't happen to be seeing this problem on a PPC box would
you? Since Linus's machine is a PPC machine too, that would support
my theory that this could be a compiler issue on that platform.
Damn, wait, Patrick, I think I know what's happening. The iptables
IPT_* verdicts are dependant upon the NF_* values, and they don't
cope with Bart's changes I bet. Can you figure out what the exact
error would be? This kind of issue would explain the looping inside
of ipt_do_table(), wouldn't it?
next prev parent reply other threads:[~2005-03-11 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 7:23 Last night Linus bk - netfilter busted? Dmitry Torokhov
2005-03-11 14:00 ` Patrick McHardy
2005-03-11 18:51 ` David S. Miller [this message]
2005-03-11 18:56 ` Dmitry Torokhov
2005-03-11 19:27 ` Sergey Vlasov
2005-03-11 20:49 ` Patrick McHardy
2005-03-11 21:21 ` Herbert Xu
2005-03-11 22:55 ` Patrick McHardy
2005-03-13 6:54 ` Dmitry Torokhov
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=20050311105136.2a5e4ddc.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dtor_core@ameritech.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.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).