public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v3 13/16] udp: Add helper to extract port from a sockaddr_in or sockaddr_in6
Date: Fri, 25 Nov 2022 18:29:13 +1100	[thread overview]
Message-ID: <20221125072916.3060938-14-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20221125072916.3060938-1-david@gibson.dropbear.id.au>

udp_sock_handler_splice() has a somewhat clunky if to extract the port from
a socket address which could be either IPv4 or IPv6.  Future changes are
going to make this even more clunky, so introduce a helper function to
do this extraction.

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
 udp.c | 26 ++++++++++++++------------
 1 file changed, 14 insertions(+), 12 deletions(-)

diff --git a/udp.c b/udp.c
index c7e05c8..03e88c5 100644
--- a/udp.c
+++ b/udp.c
@@ -497,6 +497,19 @@ static int udp_splice_new_ns(void *arg)
 	return 0;
 }
 
+/**
+ * sa_port() - Determine port from a sockaddr_in or sockaddr_in6
+ * @v6:		Is @sa a sockaddr_in6 (otherwise sockaddr_in)?
+ * @sa:		Pointer to either sockaddr_in or sockaddr_in6
+ */
+static in_port_t sa_port(bool v6, const void *sa)
+{
+	const struct sockaddr_in6 *sa6 = sa;
+	const struct sockaddr_in *sa4 = sa;
+
+	return v6 ? ntohs(sa6->sin6_port) : ntohs(sa4->sin_port);
+}
+
 /**
  * udp_sock_handler_splice() - Handler for socket mapped to "spliced" connection
  * @c:		Execution context
@@ -508,8 +521,6 @@ static void udp_sock_handler_splice(const struct ctx *c, union epoll_ref ref,
 				    uint32_t events, const struct timespec *now)
 {
 	in_port_t src, dst = ref.r.p.udp.udp.port;
-	struct msghdr *mh = &udp_mmh_recv[0].msg_hdr;
-	struct sockaddr_storage *sa_s = mh->msg_name;
 	int s, v6 = ref.r.p.udp.udp.v6, n, i;
 
 	if (!(events & EPOLLIN))
@@ -520,16 +531,7 @@ static void udp_sock_handler_splice(const struct ctx *c, union epoll_ref ref,
 	if (n <= 0)
 		return;
 
-	if (v6) {
-		struct sockaddr_in6 *sa = (struct sockaddr_in6 *)sa_s;
-
-		src = htons(sa->sin6_port);
-	} else {
-		struct sockaddr_in *sa = (struct sockaddr_in *)sa_s;
-
-		src = ntohs(sa->sin_port);
-	}
-
+	src = sa_port(v6, udp_mmh_recv[0].msg_hdr.msg_name);
 
 	if (ref.r.p.udp.udp.ns) {
 		src += c->udp.fwd_in.rdelta[src];
-- 
@@ -497,6 +497,19 @@ static int udp_splice_new_ns(void *arg)
 	return 0;
 }
 
+/**
+ * sa_port() - Determine port from a sockaddr_in or sockaddr_in6
+ * @v6:		Is @sa a sockaddr_in6 (otherwise sockaddr_in)?
+ * @sa:		Pointer to either sockaddr_in or sockaddr_in6
+ */
+static in_port_t sa_port(bool v6, const void *sa)
+{
+	const struct sockaddr_in6 *sa6 = sa;
+	const struct sockaddr_in *sa4 = sa;
+
+	return v6 ? ntohs(sa6->sin6_port) : ntohs(sa4->sin_port);
+}
+
 /**
  * udp_sock_handler_splice() - Handler for socket mapped to "spliced" connection
  * @c:		Execution context
@@ -508,8 +521,6 @@ static void udp_sock_handler_splice(const struct ctx *c, union epoll_ref ref,
 				    uint32_t events, const struct timespec *now)
 {
 	in_port_t src, dst = ref.r.p.udp.udp.port;
-	struct msghdr *mh = &udp_mmh_recv[0].msg_hdr;
-	struct sockaddr_storage *sa_s = mh->msg_name;
 	int s, v6 = ref.r.p.udp.udp.v6, n, i;
 
 	if (!(events & EPOLLIN))
@@ -520,16 +531,7 @@ static void udp_sock_handler_splice(const struct ctx *c, union epoll_ref ref,
 	if (n <= 0)
 		return;
 
-	if (v6) {
-		struct sockaddr_in6 *sa = (struct sockaddr_in6 *)sa_s;
-
-		src = htons(sa->sin6_port);
-	} else {
-		struct sockaddr_in *sa = (struct sockaddr_in *)sa_s;
-
-		src = ntohs(sa->sin_port);
-	}
-
+	src = sa_port(v6, udp_mmh_recv[0].msg_hdr.msg_name);
 
 	if (ref.r.p.udp.udp.ns) {
 		src += c->udp.fwd_in.rdelta[src];
-- 
2.38.1


  parent reply	other threads:[~2022-11-25  7:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25  7:29 [PATCH v3 00/16] Simplify and correct handling of "spliced" UDP forwarding David Gibson
2022-11-25  7:29 ` [PATCH v3 01/16] udp: Also bind() connected ports for "splice" forwarding David Gibson
2022-11-25  7:29 ` [PATCH v3 02/16] udp: Separate tracking of inbound and outbound packet flows David Gibson
2022-11-25  7:29 ` [PATCH v3 03/16] udp: Always use sendto() rather than send() for forwarding spliced packets David Gibson
2022-11-25  7:29 ` [PATCH v3 04/16] udp: Don't connect "forward" sockets for spliced flows David Gibson
2022-11-25  7:29 ` [PATCH v3 05/16] udp: Remove the @bound field from union udp_epoll_ref David Gibson
2022-11-25  7:29 ` [PATCH v3 06/16] udp: Split splice field in udp_epoll_ref into (mostly) independent bits David Gibson
2022-11-25  7:29 ` [PATCH v3 07/16] udp: Don't create double sockets for -U port David Gibson
2022-11-25  7:29 ` [PATCH v3 08/16] udp: Re-use fixed bound sockets for packet forwarding when possible David Gibson
2022-11-25  7:29 ` [PATCH v3 09/16] udp: Don't explicitly track originating socket for spliced "connections" David Gibson
2022-11-25  7:29 ` [PATCH v3 10/16] udp: Update UDP "connection" timestamps in both directions David Gibson
2022-11-25  7:29 ` [PATCH v3 11/16] udp: Simplify udp_sock_handler_splice David Gibson
2022-11-25  7:29 ` [PATCH v3 12/16] udp: Make UDP_SPLICE_FRAMES and UDP_TAP_FRAMES_MEM the same thing David Gibson
2022-11-25  7:29 ` David Gibson [this message]
2022-11-25  7:29 ` [PATCH v3 14/16] udp: Unify buffers for tap and splice paths David Gibson
2022-11-25  7:29 ` [PATCH v3 15/16] udp: Split send half of udp_sock_handler_splice() from the receive half David Gibson
2022-11-25  7:29 ` [PATCH v3 16/16] udp: Correct splice forwarding when receiving from multiple sources David Gibson
2022-11-29  5:59   ` David Gibson

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=20221125072916.3060938-14-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).