From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 04/10] tcp: Hash IPv4 and IPv4-mapped-IPv6 addresses the same
Date: Fri, 4 Nov 2022 19:43:27 +1100 [thread overview]
Message-ID: <20221104084333.3761760-5-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20221104084333.3761760-1-david@gibson.dropbear.id.au>
In the tcp_conn structure, we represent IPv4 connections with IPv4-mapped
IPv6 addresses in the single address field. However, we have different
paths which will calculate different hashes for IPv4 and equivalent
IPv4-mapped IPv6 addresses. This will cause problems for some future
changes.
Make the hash function work the same for these two cases, by always mapping
IPv4 addresses into IPv4-mapped addresses before hashing. This involves
some ugly temporaries, but later changes should improve this again.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
siphash.c | 1 +
tcp.c | 33 +++++++++++++++------------------
2 files changed, 16 insertions(+), 18 deletions(-)
diff --git a/siphash.c b/siphash.c
index 37a6d73..516a508 100644
--- a/siphash.c
+++ b/siphash.c
@@ -104,6 +104,7 @@
*
* Return: the 64-bit hash output
*/
+/* cppcheck-suppress unusedFunction */
uint64_t siphash_8b(const uint8_t *in, const uint64_t *k)
{
PREAMBLE(8);
diff --git a/tcp.c b/tcp.c
index 508d6e9..4645004 100644
--- a/tcp.c
+++ b/tcp.c
@@ -1315,30 +1315,27 @@ __attribute__((__noinline__)) /* See comment in Makefile */
static unsigned int tcp_hash(const struct ctx *c, int af, const void *addr,
in_port_t tap_port, in_port_t sock_port)
{
+ struct {
+ struct in6_addr addr;
+ in_port_t tap_port;
+ in_port_t sock_port;
+ } __attribute__((__packed__)) in = {
+ .tap_port = tap_port,
+ .sock_port = sock_port,
+ };
uint64_t b = 0;
if (af == AF_INET) {
- struct {
- struct in_addr addr;
- in_port_t tap_port;
- in_port_t sock_port;
- } __attribute__((__packed__)) in = {
- *(struct in_addr *)addr, tap_port, sock_port,
- };
-
- b = siphash_8b((uint8_t *)&in, c->tcp.hash_secret);
- } else if (af == AF_INET6) {
- struct {
- struct in6_addr addr;
- in_port_t tap_port;
- in_port_t sock_port;
- } __attribute__((__packed__)) in = {
- *(struct in6_addr *)addr, tap_port, sock_port,
- };
+ struct in6_addr v4mapped;
- b = siphash_20b((uint8_t *)&in, c->tcp.hash_secret);
+ encode_ip4mapped_ip6(&v4mapped, addr);
+ in.addr = v4mapped;
+ } else {
+ in.addr = *(struct in6_addr *)addr;
}
+ b = siphash_20b((uint8_t *)&in, c->tcp.hash_secret);
+
return (unsigned int)(b % TCP_HASH_TABLE_SIZE);
}
--
@@ -1315,30 +1315,27 @@ __attribute__((__noinline__)) /* See comment in Makefile */
static unsigned int tcp_hash(const struct ctx *c, int af, const void *addr,
in_port_t tap_port, in_port_t sock_port)
{
+ struct {
+ struct in6_addr addr;
+ in_port_t tap_port;
+ in_port_t sock_port;
+ } __attribute__((__packed__)) in = {
+ .tap_port = tap_port,
+ .sock_port = sock_port,
+ };
uint64_t b = 0;
if (af == AF_INET) {
- struct {
- struct in_addr addr;
- in_port_t tap_port;
- in_port_t sock_port;
- } __attribute__((__packed__)) in = {
- *(struct in_addr *)addr, tap_port, sock_port,
- };
-
- b = siphash_8b((uint8_t *)&in, c->tcp.hash_secret);
- } else if (af == AF_INET6) {
- struct {
- struct in6_addr addr;
- in_port_t tap_port;
- in_port_t sock_port;
- } __attribute__((__packed__)) in = {
- *(struct in6_addr *)addr, tap_port, sock_port,
- };
+ struct in6_addr v4mapped;
- b = siphash_20b((uint8_t *)&in, c->tcp.hash_secret);
+ encode_ip4mapped_ip6(&v4mapped, addr);
+ in.addr = v4mapped;
+ } else {
+ in.addr = *(struct in6_addr *)addr;
}
+ b = siphash_20b((uint8_t *)&in, c->tcp.hash_secret);
+
return (unsigned int)(b % TCP_HASH_TABLE_SIZE);
}
--
2.38.1
next prev parent reply other threads:[~2022-11-04 8:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 8:43 [PATCH 00/10] RFC: Preliminaries for using share IPv4 & IPv6 sockets David Gibson
2022-11-04 8:43 ` [PATCH 01/10] tcp: no v6 flag in ref David Gibson
2022-11-07 18:07 ` Stefano Brivio
2022-11-08 0:35 ` David Gibson
2022-11-04 8:43 ` [PATCH 02/10] tcp: Helper to encode IPv4-mapped IPv6 addresses David Gibson
2022-11-07 18:08 ` Stefano Brivio
2022-11-08 0:46 ` David Gibson
2022-11-04 8:43 ` [PATCH 03/10] tcp: Partially unify IPv4 and IPv6 paths in tcp_hash_match() David Gibson
2022-11-07 18:08 ` Stefano Brivio
2022-11-08 0:51 ` David Gibson
2022-11-04 8:43 ` David Gibson [this message]
2022-11-04 8:43 ` [PATCH 05/10] tcp: Take tcp_hash_insert() address from struct tcp_conn David Gibson
2022-11-04 8:43 ` [PATCH 06/10] tcp: Unify IPv4 and IPv6 paths for hashing and matching David Gibson
2022-11-04 8:43 ` [PATCH 07/10] tcp: Remove ugly address union from struct tcp_conn David Gibson
2022-11-07 18:08 ` Stefano Brivio
2022-11-08 0:54 ` David Gibson
2022-11-04 8:43 ` [PATCH 08/10] tcp: Unify initial sequence numbers for IPv4 and IPv6 David Gibson
2022-11-04 8:43 ` [PATCH 09/10] tcp: Have tcp_seq_init() take its parameters from struct tcp_conn David Gibson
2022-11-04 8:43 ` [PATCH 10/10] tcp: Fix small error in tcp_seq_init() time handling David Gibson
2022-11-07 18:08 ` Stefano Brivio
2022-11-08 0:59 ` David Gibson
2022-11-04 8:47 ` [PATCH 00/10] RFC: Preliminaries for using share IPv4 & IPv6 sockets Stefano Brivio
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=20221104084333.3761760-5-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).