Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com, fw@strlen.de
Subject: [PATCH net 0/4] Netfilter/IPVS fixes for net
Date: Wed, 17 Jul 2024 23:52:10 +0200	[thread overview]
Message-ID: <20240717215214.225394-1-pablo@netfilter.org> (raw)

Hi,

The following patchset contains Netfilter/IPVS fixes for net:

1) Call nf_expect_get_id() to delete expectation by ID. By trial and
   error it is possible to leak the LSB of the expectation address on
   x86_64. This bug is a leftover when converting the existing code
   to use nf_expect_get_id().

2) Incorrect initialization in pipapo set backend leads to packet
   mismatches. From Florian Westphal.

3) Extend netfilter's selftests to cover for the pipapo set backend,
   also from Florian.

4) Fix sparse warning in IPVS when adding service, from Chen Hanxiao.

Please, pull these changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git nf-24-07-17

Thanks.

----------------------------------------------------------------

The following changes since commit 0e03c643dc9389e61fa484562dae58c8d6e96d63:

  eth: fbnic: fix s390 build. (2024-07-17 06:25:14 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git tags/nf-24-07-17

for you to fetch changes up to cbd070a4ae62f119058973f6d2c984e325bce6e7:

  ipvs: properly dereference pe in ip_vs_add_service (2024-07-17 23:38:17 +0200)

----------------------------------------------------------------
netfilter pull request 24-07-17

----------------------------------------------------------------
Chen Hanxiao (1):
      ipvs: properly dereference pe in ip_vs_add_service

Florian Westphal (2):
      netfilter: nf_set_pipapo: fix initial map fill
      selftests: netfilter: add test case for recent mismatch bug

Pablo Neira Ayuso (1):
      netfilter: ctnetlink: use helper function to calculate expect ID

 net/netfilter/ipvs/ip_vs_ctl.c                     | 10 +--
 net/netfilter/nf_conntrack_netlink.c               |  3 +-
 net/netfilter/nft_set_pipapo.c                     |  4 +-
 net/netfilter/nft_set_pipapo.h                     | 21 ++++++
 net/netfilter/nft_set_pipapo_avx2.c                | 10 +--
 .../selftests/net/netfilter/nft_concat_range.sh    | 76 +++++++++++++++++++++-
 6 files changed, 111 insertions(+), 13 deletions(-)

             reply	other threads:[~2024-07-17 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 21:52 Pablo Neira Ayuso [this message]
2024-07-17 21:52 ` [PATCH net 1/4] netfilter: ctnetlink: use helper function to calculate expect ID Pablo Neira Ayuso
2024-07-18 11:40   ` patchwork-bot+netdevbpf
2024-07-17 21:52 ` [PATCH net 2/4] netfilter: nf_set_pipapo: fix initial map fill Pablo Neira Ayuso
2024-07-17 21:52 ` [PATCH net 3/4] selftests: netfilter: add test case for recent mismatch bug Pablo Neira Ayuso
2024-07-17 21:52 ` [PATCH net 4/4] ipvs: properly dereference pe in ip_vs_add_service 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=20240717215214.225394-1-pablo@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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