mbox series

[nf,0/4] NAT fixes

Message ID 20230307232259.2681135-1-jeremy@azazel.net
Headers show
Series NAT fixes | expand

Message

Jeremy Sowden March 7, 2023, 11:22 p.m. UTC 
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.

Jeremy Sowden (4):
  netfilter: nft_nat: correct length for loading protocol registers
  netfilter: nft_masq: correct length for loading protocol registers
  netfilter: nft_redir: correct length for loading protocol registers
  netfilter: nft_redir: correct value of inet type `.maxattrs`

 net/netfilter/nft_masq.c  | 2 +-
 net/netfilter/nft_nat.c   | 2 +-
 net/netfilter/nft_redir.c | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

Comments

Florian Westphal March 8, 2023, 11:14 a.m. UTC | #1 
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>
Pablo Neira Ayuso March 9, 2023, 9:27 a.m. UTC | #2 
On Tue, Mar 07, 2023 at 11:22:55PM +0000, Jeremy Sowden 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.

Applied to nf.git, thanks