lvs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: netfilter-devel@vger.kernel.org
Cc: lvs-devel@vger.kernel.org, ja@ssi.bg, horms@verge.net.au,
	Florian Westphal <fw@strlen.de>
Subject: [PATCH nf-next v2 0/4] netfilter: ipvs: remove unneeded hook wrappers
Date: Tue, 12 Oct 2021 19:29:55 +0200	[thread overview]
Message-ID: <20211012172959.745-1-fw@strlen.de> (raw)

V2: Patch 4/4 had a bug that would enter ipv6 branch for
ipv4 packets, fix that.

This series reduces the number of different hook function
implementations by merging the ipv4 and ipv6 hooks into
common code.

selftests/netfilter/ipvs.sh passes.

Florian Westphal (4):
  netfilter: ipvs: prepare for hook function reduction
  netfilter: ipvs: remove unneeded output wrappers
  netfilter: ipvs: remove unneeded input wrappers
  netfilter: ipvs: merge ipv4 + ipv6 icmp reply handlers

 net/netfilter/ipvs/ip_vs_core.c | 166 ++++++--------------------------
 1 file changed, 32 insertions(+), 134 deletions(-)

-- 
2.32.0


             reply	other threads:[~2021-10-12 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 17:29 Florian Westphal [this message]
2021-10-12 17:29 ` [PATCH nf-next v2 1/4] netfilter: ipvs: prepare for hook function reduction Florian Westphal
2021-10-12 17:29 ` [PATCH nf-next v2 2/4] netfilter: ipvs: remove unneeded output wrappers Florian Westphal
2021-10-12 17:29 ` [PATCH nf-next v2 3/4] netfilter: ipvs: remove unneeded input wrappers Florian Westphal
2021-10-12 17:29 ` [PATCH nf-next v2 4/4] netfilter: ipvs: merge ipv4 + ipv6 icmp reply handlers Florian Westphal
2021-10-12 20:38 ` [PATCH nf-next v2 0/4] netfilter: ipvs: remove unneeded hook wrappers Julian Anastasov
2021-10-17 12:17   ` Simon Horman
2021-10-14 21:02 ` 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=20211012172959.745-1-fw@strlen.de \
    --to=fw@strlen.de \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@vger.kernel.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).