All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Oester <kernel@linuxace.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] iptables: spurious error in load_extension
Date: Sun, 3 Nov 2013 21:26:06 +0100	[thread overview]
Message-ID: <20131103202606.GA31495@localhost> (raw)
In-Reply-To: <20131008162015.GB18402@home>

On Tue, Oct 08, 2013 at 09:20:15AM -0700, Phil Oester wrote:
> In commit 927385017047d (iptables: improve error reporting with extension
> loading troubles), a new error message was added in an attempt to handle
> the case where a match does not support a particular protocol family. 
> For instance, attempting to use the osf match on IPv6.
> 
> Unfortunately, this error message now triggers when creating a new chain
> which has the same name as a match extension, because iptables calls
> xtables_find_target with the name of the new chain to verify it does not
> clash with an existing target.  For example:
> 
>     # iptables -N tcp
>     /usr/lib/xtables/libxt_tcp.so: no "tcp" extension found for this protocol
> 
> I attempted to resolve this by adding a new XTF flag, but that required changes
> in many different places (including -j handling).  It seems easiest just to
> remove this warning and stick with the original error message of ENOENT, even
> if less than precise.

Also applied, thanks Phil.

      reply	other threads:[~2013-11-03 20:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 16:20 [PATCH] iptables: spurious error in load_extension Phil Oester
2013-11-03 20:26 ` Pablo Neira Ayuso [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=20131103202606.GA31495@localhost \
    --to=pablo@netfilter.org \
    --cc=kernel@linuxace.com \
    --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.