public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 2/7] udp_flow: Assign socket to flow inside udp_flow_sock()
Date: Sat, 20 Dec 2025 20:43:35 +1100	[thread overview]
Message-ID: <aUZvx-Dnz_xGPIBe@zatzit> (raw)
In-Reply-To: <20251219164518.930012-3-lvivier@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]

On Fri, Dec 19, 2025 at 05:45:13PM +0100, Laurent Vivier wrote:
> Move the assignment of uflow->s[sidei] from the caller (udp_flow_new())
> into udp_flow_sock() itself, placing it after the successful connect().
> 
> This is a pure refactoring with no functional change.  The socket fd is
> now assigned within udp_flow_sock() where the socket is created, rather
> than requiring the caller to capture the return value.  On error paths,
> uflow->s[sidei] remains at its initialized value of -1 rather than being
> set to the negative error code, which is semantically cleaner (though
> functionally equivalent given the >= 0 check in udp_flow_close()).
> 
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

> ---
>  udp_flow.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/udp_flow.c b/udp_flow.c
> index 8907f2f72741..33f29f21e69e 100644
> --- a/udp_flow.c
> +++ b/udp_flow.c
> @@ -109,6 +109,7 @@ static int udp_flow_sock(const struct ctx *c,
>  		flow_dbg_perror(uflow, "Couldn't connect flow socket");
>  		return rc;
>  	}
> +	uflow->s[sidei] = s;
>  
>  	/* It's possible, if unlikely, that we could receive some packets in
>  	 * between the bind() and connect() which may or may not be for this
> @@ -163,7 +164,7 @@ static flow_sidx_t udp_flow_new(const struct ctx *c, union flow *flow,
>  
>  	flow_foreach_sidei(sidei) {
>  		if (pif_is_socket(uflow->f.pif[sidei]))
> -			if ((uflow->s[sidei] = udp_flow_sock(c, uflow, sidei)) < 0)
> +			if (udp_flow_sock(c, uflow, sidei) < 0)
>  				goto cancel;
>  	}
>  
> -- 
> 2.51.1
> 

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-12-20  9:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 16:45 [PATCH 0/7] flow: Introduce flow_epoll_set() to centralize epoll operations Laurent Vivier
2025-12-19 16:45 ` [PATCH 1/7] tcp: Update EPOLL_TYPE_TCP_TIMER fd Laurent Vivier
2025-12-20  7:40   ` David Gibson
2025-12-19 16:45 ` [PATCH 2/7] udp_flow: Assign socket to flow inside udp_flow_sock() Laurent Vivier
2025-12-20  9:43   ` David Gibson [this message]
2025-12-19 16:45 ` [PATCH 3/7] tcp_splice: Refactor tcp_splice_conn_epoll_events() to per-side computation Laurent Vivier
2025-12-19 16:45 ` [PATCH 4/7] flow: Introduce flow_epoll_set() to centralize epoll operations Laurent Vivier
2025-12-19 16:45 ` [PATCH 5/7] flow: Use epoll_id_to_fd[EPOLLFD_ID_DEFAULT] in flow_epollid_set() Laurent Vivier
2025-12-19 16:45 ` [PATCH 6/7] flow: Compute epoll events inside flow_epoll_set() Laurent Vivier
2025-12-19 16:45 ` [PATCH 7/7] flow: Have flow_epoll_set() retrieve file descriptor from flow structure Laurent Vivier

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=aUZvx-Dnz_xGPIBe@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    /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).