From: Stefano Brivio <sbrivio@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v3 9/9] tcp: Introduce ipv4_fill_headers()/ipv6_fill_headers()
Date: Thu, 29 Feb 2024 17:29:59 +0100 [thread overview]
Message-ID: <20240229172959.797f4ca0@elisabeth> (raw)
In-Reply-To: <20240217150725.661467-10-lvivier@redhat.com>
On Sat, 17 Feb 2024 16:07:25 +0100
Laurent Vivier <lvivier@redhat.com> wrote:
> Replace the macro SET_TCP_HEADER_COMMON_V4_V6() by a new function
> tcp_fill_header().
>
> Move IPv4 and IPv6 code from tcp_l2_buf_fill_headers() to
> tcp_fill_ipv4_header() and tcp_fill_ipv6_header()
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
>
> Notes:
> v3:
> - add to sub-series part 1
>
> v2:
> - extract header filling functions from
> "tcp: extract buffer management from tcp_send_flag()"
> - rename them tcp_fill_flag_header()/tcp_fill_ipv4_header(),
> tcp_fill_ipv6_header()
> - use upside-down Christmas tree arguments order
> - replace (void *) by (struct tcphdr *)
>
> tcp.c | 154 +++++++++++++++++++++++++++++++++++++++-------------------
> 1 file changed, 104 insertions(+), 50 deletions(-)
>
> diff --git a/tcp.c b/tcp.c
> index aa03c20712f6..bc57a4f6e611 100644
> --- a/tcp.c
> +++ b/tcp.c
> @@ -1324,6 +1324,108 @@ void tcp_defer_handler(struct ctx *c)
> tcp_l2_data_buf_flush(c);
> }
>
> +/**
> + * tcp_fill_header() - Fill the TCP header fields for a given TCP segment.
> + *
> + * @th: Pointer to the TCP header structure
> + * @conn: Pointer to the TCP connection structure
> + * @seq: Sequence number
> + */
> +static void tcp_fill_header(struct tcphdr *th,
> + const struct tcp_tap_conn *conn, uint32_t seq)
> +{
> + th->source = htons(conn->fport);
> + th->dest = htons(conn->eport);
> + th->seq = htonl(seq);
> + th->ack_seq = htonl(conn->seq_ack_to_tap);
> + if (conn->events & ESTABLISHED) {
> + th->window = htons(conn->wnd_to_tap);
> + } else {
> + unsigned wnd = conn->wnd_to_tap << conn->ws_to_tap;
> +
> + th->window = htons(MIN(wnd, USHRT_MAX));
> + }
> +}
> +
> +/**
> + * tcp_fill_ipv4_header() - Fill 802.3, IPv4, TCP headers in pre-cooked buffers
> + * @c: Execution context
> + * @conn: Connection pointer
> + * @iph: Pointer to IPv4 header, immediately followed by a TCP header
> + * @plen: Payload length (including TCP header options)
> + * @check: Checksum, if already known
> + * @seq: Sequence number for this segment
> + *
> + * Return: IP frame length including L2 headers, host order
> + */
> +static size_t tcp_fill_ipv4_header(const struct ctx *c,
> + const struct tcp_tap_conn *conn,
> + struct iphdr *iph, size_t plen,
> + const uint16_t *check, uint32_t seq)
> +{
> + size_t ip_len = plen + sizeof(struct iphdr) + sizeof(struct tcphdr);
> + const struct in_addr *a4 = inany_v4(&conn->faddr);
> + struct tcphdr *th = (struct tcphdr *)(iph + 1);
> +
> + iph->tot_len = htons(ip_len);
> + iph->saddr = a4->s_addr;
The reasoning behind the fact that a4 isn't NULL here is relatively
simple to follow: you already check for inany_v4(&conn->faddr) in the
caller, if it evaluates to true, you call this.
Still, it's a bit too convoluted for Coverity's taste. Could you
perhaps add an ASSERT(a4) before this block to make it obvious? It's a
bit annoying that we extract the address twice, but I don't see a much
better alternative compared to what you did.
--
Stefano
next prev parent reply other threads:[~2024-02-29 16:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 15:07 [PATCH v3 0/9] Add vhost-user support to passt (part 1) Laurent Vivier
2024-02-17 15:07 ` [PATCH v3 1/9] iov: add some functions to manage iovec Laurent Vivier
2024-02-19 2:45 ` David Gibson
2024-02-17 15:07 ` [PATCH v3 2/9] pcap: add pcap_iov() Laurent Vivier
2024-02-19 2:50 ` David Gibson
2024-02-17 15:07 ` [PATCH v3 3/9] checksum: align buffers Laurent Vivier
2024-02-17 15:07 ` [PATCH v3 4/9] checksum: add csum_iov() Laurent Vivier
2024-02-19 2:52 ` David Gibson
2024-02-17 15:07 ` [PATCH v3 5/9] util: move IP stuff from util.[ch] to ip.[ch] Laurent Vivier
2024-02-19 2:59 ` David Gibson
2024-02-17 15:07 ` [PATCH v3 6/9] checksum: use csum_ip4_header() in udp.c and tcp.c Laurent Vivier
2024-02-19 3:01 ` David Gibson
2024-02-29 16:24 ` Stefano Brivio
2024-02-29 23:10 ` David Gibson
2024-03-01 7:58 ` Stefano Brivio
2024-03-01 12:23 ` David Gibson
2024-03-04 17:04 ` Stefano Brivio
2024-02-17 15:07 ` [PATCH v3 7/9] checksum: introduce functions to compute the header part checksum for TCP/UDP Laurent Vivier
2024-02-19 3:08 ` David Gibson
2024-02-28 13:26 ` Laurent Vivier
2024-02-29 0:38 ` David Gibson
2024-02-29 7:05 ` Stefano Brivio
2024-02-29 8:49 ` David Gibson
2024-02-29 8:56 ` Stefano Brivio
2024-02-29 14:15 ` Stefano Brivio
2024-02-29 23:09 ` David Gibson
2024-03-01 6:56 ` Stefano Brivio
2024-03-04 1:54 ` David Gibson
2024-03-04 11:00 ` Stefano Brivio
2024-03-04 22:47 ` Stefano Brivio
2024-03-06 5:09 ` David Gibson
2024-03-08 0:08 ` Stefano Brivio
2024-03-08 1:20 ` David Gibson
2024-02-17 15:07 ` [PATCH v3 8/9] tap: make tap_update_mac() generic Laurent Vivier
2024-02-17 15:07 ` [PATCH v3 9/9] tcp: Introduce ipv4_fill_headers()/ipv6_fill_headers() Laurent Vivier
2024-02-19 3:14 ` David Gibson
2024-02-29 16:29 ` Stefano Brivio [this message]
2024-02-29 16:31 ` [PATCH v3 0/9] Add vhost-user support to passt (part 1) 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=20240229172959.797f4ca0@elisabeth \
--to=sbrivio@redhat.com \
--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).