From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] evaluate: maps: check element data mapping matches set data definition
Date: Tue, 22 Jul 2025 04:05:07 +0200 [thread overview]
Message-ID: <aH7x02JC0l2u3bn0@calendula> (raw)
In-Reply-To: <20250721105721.2512-1-fw@strlen.de>
On Mon, Jul 21, 2025 at 12:57:07PM +0200, Florian Westphal wrote:
> This change is similar to
> 7f4d7fef31bd ("evaluate: check element key vs. set definition")
>
> but this time for data mappings.
>
> The included bogon asserts with:
> BUG: invalid data expression type catch-all set element
> nft: src/netlink.c:596: __netlink_gen_data: Assertion `0' failed.
>
> after:
> internal:0:0-0: Error: Element mapping mismatches map definition, expected packet mark, not 'invalid'
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Reviewed-by: Pablo Neira Ayuso <pablo@netfilter.org>
prev parent reply other threads:[~2025-07-22 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 10:57 [PATCH nft] evaluate: maps: check element data mapping matches set data definition Florian Westphal
2025-07-22 2:05 ` 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=aH7x02JC0l2u3bn0@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).