From: Florian Westphal <fw@strlen.de>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft 0/3] parser: fix scope closing with > 1 nested scope
Date: Mon, 27 Jun 2022 12:23:16 +0200 [thread overview]
Message-ID: <20220627102316.GA23400@breakpoint.cc> (raw)
In-Reply-To: <20220624092555.1572-1-fw@strlen.de>
Florian Westphal <fw@strlen.de> wrote:
> This resolves the parsing problem reported by Phil.
> First patch is his test case, second patch is an
> (unrelated) fix for SYNPROXY scoping (lack of close).
>
> Last patch fixes closing with nested scopes, where we exited
> a scope too early.
>
> Florian Westphal (2):
> parser: add missing synproxy scope closure
> scanner: don't pop active flex scanner scope
>
> Phil Sutter (1):
> tests/py: Add a test for failing ipsec after counter
Pushed to nftables.git
prev parent reply other threads:[~2022-06-27 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 9:25 [PATCH nft 0/3] parser: fix scope closing with > 1 nested scope Florian Westphal
2022-06-24 9:25 ` [PATCH nft 1/3] tests/py: Add a test for failing ipsec after counter Florian Westphal
2022-06-24 9:25 ` [PATCH nft 2/3] parser: add missing synproxy scope closure Florian Westphal
2022-06-24 9:25 ` [PATCH nft 3/3] scanner: don't pop active flex scanner scope Florian Westphal
2022-06-27 10:23 ` 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=20220627102316.GA23400@breakpoint.cc \
--to=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 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.