All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Martin Zatloukal <slezi2@pvfree.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: list vmap counter errot
Date: Thu, 16 Sep 2021 11:27:02 +0200	[thread overview]
Message-ID: <20210916092702.GA31336@salvia> (raw)
In-Reply-To: <ec914466-169b-b146-c216-e1faf1159068@pvfree.net>

Hi,

On Thu, Sep 16, 2021 at 10:38:03AM +0200, Martin Zatloukal wrote:
> 
> hi. i am trying nftables for our igw and i ran into a problem.
> 
> add map ip filter forwport { type ipv4_addr . inet_proto . inet_service:
> verdict; flags interval; counter;  }
> 
> add rule ip filter FORWARD iifname $INET_IFACE ip daddr . ip protocol  . th
> dport vmap @forwport counter
> 
> if I enter
> 
> nft list ruleset
> 
> then cli send : Unauthorized Memory Access (SIGSEGV)
> 
> 
> dmesg
> 
> [ 1056.857354] nft[1069]: segfault at 10 ip 00007f44edde176d sp
> 00007ffc2cdb8fa0 error 4 in libnftables.so.1.1.0[7f44eddd8000+62000]
> 
> [ 1056.857362] Code: 89 68 10 48 89 50 38 48 83 c4 08 5b 5d c3 66 66 2e 0f
> 1f 84 00 00 00 00 00 0f 1f 40 00 48 85 ff 74 23 55 48 8b 47 10 48 89 fd <48>
> 8b 40 10 48 85 c0 74 02 ff d0 48 89 ef 5d e9 2f a4 02 00 0f 1f
> 
> if map not use flags counter,is listing ok
> 
> debian 11
> 
> libnftables1_1.0.0-1_amd64.deb
> nftables_1.0.0-1_amd64.deb

I cannot reproduce this here, valgrind and ASAN outputs are perfectly
clean?

Could you post you ldd /usr/sbin/nft output? Could you run 'nft list
ruleset' inside valgrind?  Or there is any rule that is missing in
your setup to reproduce what you are observing?

  reply	other threads:[~2021-09-16  9:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  8:38 list vmap counter errot Martin Zatloukal
2021-09-16  9:27 ` Pablo Neira Ayuso [this message]
     [not found]   ` <d02072df-d5e5-b76d-0003-0a6ef62f5d00@pvfree.net>
     [not found]     ` <20210916120005.GB11941@salvia>
2021-09-16 12:00       ` Pablo Neira Ayuso
2021-09-16 12: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=20210916092702.GA31336@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=slezi2@pvfree.net \
    /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.