From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: Francis.Dupont@fdupont.fr, linux-kernel@vger.kernel.org,
coreteam@netfilter.org, Francis_Dupont@isc.org,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: netfilter spurious ELOOP
Date: Wed, 25 Mar 2009 18:07:36 +0100 [thread overview]
Message-ID: <49CA64D8.9040602@trash.net> (raw)
In-Reply-To: <20090324.162808.114465835.davem@davemloft.net>
David Miller wrote:
> From: Francis Dupont <Francis.Dupont@fdupont.fr>
> Date: Wed, 25 Mar 2009 00:02:05 +0100
>
> Adding correct CC:'s
>
>> summary: iptables command gets spurious ELOOP errors
>>
>> report: when a rule with a target like MARK --set-mark 0x80000001
>> then adding new other rules can failed with "Too many levels of symbolic
>> links" (aka ELOOP) error.
>> The problem is in kernel net/ipv4/netfilter/ip_tables.c in the
>> mark_source_chains() routine which checks the verdict field of
>> targets even for not standard targets.
>>
>> keywords: netfilter target eloop
>>
>> environment: recent gentoo and fedora. Problem not fixed in
>> linux-2.6.29 (last stable version taken from kernel.org some minutes ago).
Just to clarify: does the problem happens when you have the MARK rule
above in a user-defined chain that has more then one jump leading to
it or does it also happen in other cases?
next prev parent reply other threads:[~2009-03-25 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 23:02 netfilter spurious ELOOP Francis Dupont
2009-03-24 23:28 ` David Miller
2009-03-25 17:07 ` Patrick McHardy [this message]
2009-03-25 17:37 ` Francis Dupont
2009-03-25 18:12 ` Patrick McHardy
2009-03-25 18:38 ` Patrick McHardy
2009-03-25 18:41 ` Patrick McHardy
2009-03-26 15:22 ` Thomas Jarosch
2009-03-26 15:25 ` Patrick McHardy
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=49CA64D8.9040602@trash.net \
--to=kaber@trash.net \
--cc=Francis.Dupont@fdupont.fr \
--cc=Francis_Dupont@isc.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.