From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Kamil Jońca" <kjonca@op.pl>
Cc: netfilter@vger.kernel.org
Subject: Re: nft ends with error
Date: Wed, 22 Nov 2023 22:04:04 +0100 [thread overview]
Message-ID: <ZV5sxC/YNUDeFgcE@calendula> (raw)
In-Reply-To: <8734wxtz3k.fsf@alfa.kjonca>
On Wed, Nov 22, 2023 at 07:35:59PM +0100, Kamil Jońca wrote:
> sudo nft --version
> nftables v1.0.9 (Old Doc Yak #3)
>
> Recently my nftables debian service started to ends with error:
>
> --8<---------------cut here---------------start------------->8---
> Nov 22 19:18:56 alfa systemd[1]: Starting nftables.service - nftables...
> Nov 22 19:18:57 alfa nft[2242551]: nft: datatype.c:1264: datatype_free: Assertion `dtype->refcnt != 0' failed.
> Nov 22 19:18:57 alfa systemd[1]: nftables.service: Failed with result 'signal'.
> Nov 22 19:18:57 alfa systemd[1]: Failed to start nftables.service - nftables.
>
> --8<---------------cut here---------------end--------------->8---
>
> After some investigating I found that nft does not like definition;
>
> --8<---------------cut here---------------start------------->8---
> table ip filter {
> ...
> map ipsec_in {
> typeof ipsec in reqid . iif : verdict
> flags interval
> }
> ...
>
> chain INPUT {
> type filter hook input priority 0; policy drop
> ...
> ipsec in reqid . iif vmap @ipsec_in
> ...
> }
> ...
> }
> --8<---------------cut here---------------end--------------->8---
>
> rules seems to be loaded entirely and works.
Thanks for this reproducer. Proposed fix:
https://patchwork.ozlabs.org/project/netfilter-devel/patch/20231122210106.183932-1-pablo@netfilter.org/
next prev parent reply other threads:[~2023-11-22 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 18:35 nft ends with error Kamil Jońca
2023-11-22 21:04 ` Pablo Neira Ayuso [this message]
2023-11-23 21:33 ` Pablo Neira Ayuso
2024-03-16 18:40 ` Kamil Jońca
2024-03-18 9:47 ` 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=ZV5sxC/YNUDeFgcE@calendula \
--to=pablo@netfilter.org \
--cc=kjonca@op.pl \
--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