From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Martin Bednar <martin@serafean.cz>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables kernel bug
Date: Tue, 29 Nov 2016 23:54:30 +0100 [thread overview]
Message-ID: <20161129225430.GA8487@salvia> (raw)
In-Reply-To: <2097005.VXRZyRJPl3@nemmerle>
On Tue, Nov 29, 2016 at 11:37:21PM +0100, Martin Bednar wrote:
> Hi, I just hit a kernel bug using nftables.
> Using kernel 4.8.11.
>
> Inline is a minimal configuration file to reproduce and the dmesg log.
> Let me know if you need anything else.
>
> Martin.
>
> Minimal configuration to reproduce:
>
> table inet filter{
> map iface_rules {type iface_index : verdict;}
> chain lan1{
> }
>
> chain input{
> type filter hook input priority 0;policy accept;
>
> iif vmap @iface_rules
>
> }
> }
> add element inet filter iface_rules {enp0s18 : jump lan1 } #BUG_ON here.
Fixed by:
http://git.kernel.org/cgit/linux/kernel/git/pablo/nf.git/commit/?id=58c78e104d937c1f560fb10ed9bb2dcde0db4fcf
Will pass this to -stable asap.
Thanks for reporting.
next prev parent reply other threads:[~2016-11-29 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 22:37 nftables kernel bug Martin Bednar
2016-11-29 22:54 ` Pablo Neira Ayuso [this message]
2016-11-29 23:28 ` Martin Bednar
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=20161129225430.GA8487@salvia \
--to=pablo@netfilter.org \
--cc=martin@serafean.cz \
--cc=netfilter@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