From: Florian Westphal <fw@strlen.de>
To: Jeremy Sowden <jeremy@azazel.net>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nf 0/4] NAT fixes
Date: Wed, 8 Mar 2023 12:14:40 +0100 [thread overview]
Message-ID: <20230308111440.GA2253@breakpoint.cc> (raw)
In-Reply-To: <20230307232259.2681135-1-jeremy@azazel.net>
Jeremy Sowden <jeremy@azazel.net> wrote:
> These bug-fixes were originally part of a larger series adding shifted
> port-ranges to nft NAT and targetting nf-next, but Florian suggested
> sending them via nf instead to get them upstream more quickly.
>
> * Patches 1-3 correct the sizes in `nft_parse_register_load` calls in
> nft_nat, nft_masq and nft_redir.
> * Patch 4 corrects a C&P mistake in an nft_redir `nft_expr_type`
> definition.
Reviewed-by: Florian Westphal <fw@strlen.de>
next prev parent reply other threads:[~2023-03-08 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 23:22 [PATCH nf 0/4] NAT fixes Jeremy Sowden
2023-03-07 23:22 ` [PATCH nf 1/4] netfilter: nft_nat: correct length for loading protocol registers Jeremy Sowden
2023-03-07 23:22 ` [PATCH nf 2/4] netfilter: nft_masq: " Jeremy Sowden
2023-03-07 23:22 ` [PATCH nf 3/4] netfilter: nft_redir: " Jeremy Sowden
2023-03-07 23:22 ` [PATCH nf 4/4] netfilter: nft_redir: correct value of inet type `.maxattrs` Jeremy Sowden
2023-03-08 11:14 ` Florian Westphal [this message]
2023-03-09 9:27 ` [PATCH nf 0/4] NAT fixes 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=20230308111440.GA2253@breakpoint.cc \
--to=fw@strlen.de \
--cc=jeremy@azazel.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