Linux Netfilter development
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Adrian Moisey <adrian@changeover.za.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] payload: restore is_raw flag for th expressions parsed from udata
Date: Mon, 21 Sep 2026 20:50:13 +0200	[thread overview]
Message-ID: <arF8ZZGEPiT7VgrF@strlen.de> (raw)
In-Reply-To: <20260825191048.95426-1-adrian@changeover.za.net>

Adrian Moisey <adrian@changeover.za.net> wrote:
> payload_expr_parse_udata() restores the pseudo transport header (th)
> proto desc from set userdata, but not payload.is_raw. The bison and
> json parsers both set is_raw for raw th expressions, which makes
> evaluation skip the transport protocol conflict check. Without it,
> re-evaluating a map declared with 'typeof ... th dport ...' from a
> later transaction fails with a bogus
> 
>   conflicting transport layer protocols specified: tcp vs. th
> 
> Set is_raw when the restored desc is proto_th, just like the parsers
> do.
> 
> Signed-off-by: Adrian Moisey <adrian@changeover.za.net>
> ---
>  src/payload.c                                 |  3 ++
>  .../testcases/maps/typeof_maps_restore_0      | 28 +++++++++++++++++++
>  2 files changed, 31 insertions(+)
>  create mode 100755 tests/shell/testcases/maps/typeof_maps_restore_0

Hint: "run-tests.sh -g" also generates the dump files.

Just mentioning this for future submissions, patch is applied,
thanks.

      reply	other threads:[~2026-09-21 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 19:10 [PATCH nft] payload: restore is_raw flag for th expressions parsed from udata Adrian Moisey
2026-09-21 18:50 ` Florian Westphal [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=arF8ZZGEPiT7VgrF@strlen.de \
    --to=fw@strlen.de \
    --cc=adrian@changeover.za.net \
    --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