From: Julian Anastasov <ja@ssi.bg>
To: tt roxy <roxy520tt@gmail.com>
Cc: Ren Wei <n05ec@lzu.edu.cn>,
lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org,
yuantan098@gmail.com, yifanwucs@gmail.com,
tomapufckgml@gmail.com, bird@lzu.edu.cn
Subject: [PATCH RFC nf v2 1/2] ipvs: do not propagate one_packet flag to hashed conns
Date: Thu, 2 Jul 2026 00:25:19 +0300 [thread overview]
Message-ID: <20260701212520.3634-1-ja@ssi.bg> (raw)
In-Reply-To: <CALMqdkR704S2BG_QD_bgHTFp2+1QCi7n0T4zoZyTo8mDZevYSA@mail.gmail.com>
Signed-off-by: Julian Anastasov <ja@ssi.bg>
---
This patch is just to help the testing of both patches. You will
replace it with your own patch that should allow the second
patch to be applied. Let me know if you see any problems.
net/netfilter/ipvs/ip_vs_conn.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/net/netfilter/ipvs/ip_vs_conn.c b/net/netfilter/ipvs/ip_vs_conn.c
index cb36641f8d1c..c916eedd69c1 100644
--- a/net/netfilter/ipvs/ip_vs_conn.c
+++ b/net/netfilter/ipvs/ip_vs_conn.c
@@ -1014,6 +1014,9 @@ ip_vs_bind_dest(struct ip_vs_conn *cp, struct ip_vs_dest *dest)
flags = cp->flags;
/* Bind with the destination and its corresponding transmitter */
if (flags & IP_VS_CONN_F_SYNC) {
+ /* Synced conns are hashed, so they can not get this flag */
+ conn_flags &= ~IP_VS_CONN_F_ONE_PACKET;
+
/* if the connection is not template and is created
* by sync, preserve the activity flag.
*/
--
2.54.0
next prev parent reply other threads:[~2026-07-01 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1782540466.git.roxy520tt@gmail.com>
2026-06-27 16:05 ` [PATCH 1/1] ipvs: preserve conn hash flags when late-binding dest Ren Wei
2026-06-27 20:46 ` Julian Anastasov
2026-06-28 5:44 ` tt roxy
2026-06-30 19:36 ` [PATCH RFC nf 1/2] ipvs: do not propagate one_packet flag to hashed conns Julian Anastasov
2026-06-30 19:36 ` [PATCH RFC nf 2/2] ipvs: adjust double hashing when fwd method changes Julian Anastasov
2026-06-30 21:40 ` Julian Anastasov
2026-07-01 21:25 ` Julian Anastasov [this message]
2026-07-01 21:25 ` [PATCH RFC nf v2 " Julian Anastasov
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=20260701212520.3634-1-ja@ssi.bg \
--to=ja@ssi.bg \
--cc=bird@lzu.edu.cn \
--cc=lvs-devel@vger.kernel.org \
--cc=n05ec@lzu.edu.cn \
--cc=netfilter-devel@vger.kernel.org \
--cc=roxy520tt@gmail.com \
--cc=tomapufckgml@gmail.com \
--cc=yifanwucs@gmail.com \
--cc=yuantan098@gmail.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 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.