All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>,
	Netfilter Development Mailing list
	<netfilter-devel@vger.kernel.org>,
	Patrick McHardy <kaber@trash.net>,
	fw@strlen.de
Subject: Re: [nft] segfault bug in simple ruleset, regression?
Date: Wed, 9 Sep 2015 17:29:24 +0200	[thread overview]
Message-ID: <20150909152924.GB24810@breakpoint.cc> (raw)
In-Reply-To: <20150909142903.GA3447@salvia>

Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > flush ruleset
> > table inet filter {
> >         chain test0 {
> >         }
> > 
> >         chain test1 {
> >         }
> > 
> >         chain test2 {
> >         }
> > 
> >         chain test {
> >                 oif vmap {
> >                         eth0 : jump test0,
> >                         eth1 : jump test1,
> >                         eth2 : jump test2
> >                 }
> >         }
> > }
> > ========== 8< ==========
> > 
> > loaded with:
> >  % nft -f file
> 
> I cannot reproduce this here using this:

I can reproduce it, but with slight tweak.

flush ruleset
table inet filter {
        chain test0 {
        }
        chain test {
                oif vmap {
                        eth0 : jump test0,
                }
        }
}

(load it with nft -f )

Then edit file to add 2nd chain:
flush ruleset
table inet filter {
        chain test0 {
        }
        chain test1 {
        }
        chain test {
                oif vmap {
                        eth0 : jump test0,
                        lo: jump test1,
                }
        }
}

load it. poof..

  reply	other threads:[~2015-09-09 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 11:28 [nft] segfault bug in simple ruleset, regression? Arturo Borrero Gonzalez
2015-09-09 14:29 ` Pablo Neira Ayuso
2015-09-09 15:29   ` Florian Westphal [this message]
2015-09-09 16:01     ` Pablo Neira Ayuso

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=20150909152924.GB24810@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=arturo.borrero.glez@gmail.com \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@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 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.