From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 09/12] icmp: Consolidate icmp_sock_handler() with icmpv6_sock_handler()
Date: Sat, 6 Jan 2024 17:00:44 +0100 [thread overview]
Message-ID: <20240106170044.0aa57f62@elisabeth> (raw)
In-Reply-To: <20231221065327.1307827-10-david@gibson.dropbear.id.au>
On Thu, 21 Dec 2023 17:53:24 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> Currently we have separate handlers for ICMP and ICMPv6 ping replies.
> Although there are a number of points of difference, with some creative
> refactoring we can combine these together sensibly. Although it doesn't
> save a vast amount of code, it does make it clearer that we're performing
> basically the same steps for each case.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> icmp.c | 90 ++++++++++++++++++++++-----------------------------------
> icmp.h | 3 +-
> passt.c | 4 +--
> 3 files changed, 37 insertions(+), 60 deletions(-)
>
> diff --git a/icmp.c b/icmp.c
> index f6c744a..b26c61f 100644
> --- a/icmp.c
> +++ b/icmp.c
> @@ -57,85 +57,63 @@ struct icmp_id_sock {
> static struct icmp_id_sock icmp_id_map[IP_VERSIONS][ICMP_NUM_IDS];
>
> /**
> - * icmp_sock_handler() - Handle new data from IPv4 ICMP socket
> + * icmp_sock_handler() - Handle new data from ICMP or ICMPv6 socket
> * @c: Execution context
> + * @af: Address family (AF_INET or AF_INET6)
> * @ref: epoll reference
> */
> -void icmp_sock_handler(const struct ctx *c, union epoll_ref ref)
> +void icmp_sock_handler(const struct ctx *c, int af, union epoll_ref ref)
> {
> + struct icmp_id_sock *const id_map = af == AF_INET
> + ? &icmp_id_map[V4][ref.icmp.id] : &icmp_id_map[V6][ref.icmp.id];
> + const char *const pname = af == AF_INET ? "ICMP" : "ICMPv6";
> char buf[USHRT_MAX];
> - struct icmphdr *ih = (struct icmphdr *)buf;
> - struct sockaddr_in sr;
> + union {
> + struct sockaddr sa;
> + struct sockaddr_in sa4;
> + struct sockaddr_in6 sa6;
> + } sr;
> socklen_t sl = sizeof(sr);
> - uint16_t seq, id;
> + uint16_t seq;
> ssize_t n;
>
> if (c->no_icmp)
> return;
>
> - n = recvfrom(ref.fd, buf, sizeof(buf), 0, (struct sockaddr *)&sr, &sl);
> + n = recvfrom(ref.fd, buf, sizeof(buf), 0, &sr.sa, &sl);
> if (n < 0)
> return;
>
> - seq = ntohs(ih->un.echo.sequence);
> -
> - /* Adjust the packet to have the ID the guest was using, rather than the
> - * host chosen value */
> - id = ref.icmp.id;
> - ih->un.echo.id = htons(id);
> + if (af == AF_INET) {
> + struct icmphdr *ih4 = (struct icmphdr *)buf;
>
> - if (c->mode == MODE_PASTA) {
> - if (icmp_id_map[V4][id].seq == seq)
> - return;
> + /* Adjust packet back to guest-side ID */
> + ih4->un.echo.id = htons(ref.icmp.id);
> + seq = ntohs(ih4->un.echo.sequence);
> + } else if (af == AF_INET6) {
> + struct icmp6hdr *ih6 = (struct icmp6hdr *)buf;
>
> - icmp_id_map[V4][id].seq = seq;
> + /* Adjust packet back to guest-side ID */
> + ih6->icmp6_identifier = htons(ref.icmp.id);
> + seq = ntohs(ih6->icmp6_sequence);
> + } else {
> + ASSERT(0);
> }
>
> - debug("ICMP: echo reply to tap, ID: %i, seq: %i", id, seq);
> -
> - tap_icmp4_send(c, sr.sin_addr, tap_ip4_daddr(c), buf, n);
> -}
> -
> -/**
> - * icmpv6_sock_handler() - Handle new data from ICMPv6 socket
> - * @c: Execution context
> - * @ref: epoll reference
> - */
> -void icmpv6_sock_handler(const struct ctx *c, union epoll_ref ref)
> -{
> - char buf[USHRT_MAX];
> - struct icmp6hdr *ih = (struct icmp6hdr *)buf;
> - struct sockaddr_in6 sr;
> - socklen_t sl = sizeof(sr);
> - uint16_t seq, id;
> - ssize_t n;
> -
> - if (c->no_icmp)
> - return;
> -
> - n = recvfrom(ref.fd, buf, sizeof(buf), 0, (struct sockaddr *)&sr, &sl);
> - if (n < 0)
> - return;
> -
> - seq = ntohs(ih->icmp6_sequence);
> -
> - /* Adjust the packet to have the ID the guest was using, rather than the
> - * host chosen value */
> - id = ref.icmp.id;
> - ih->icmp6_identifier = htons(id);
> -
> - /* In PASTA mode, we'll get any reply we send, discard them. */
> if (c->mode == MODE_PASTA) {
The comment here should be kept -- the kernel behaviour was rather
surprising to me, and I would have otherwise no idea why we return
early here.
--
Stefano
next prev parent reply other threads:[~2024-01-06 16:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 6:53 [PATCH v2 00/12] RFC: ICMP reworks preliminary to flow table integration David Gibson
2023-12-21 6:53 ` [PATCH v2 01/12] checksum: Don't use linux/icmp.h when netinet/ip_icmp.h will do David Gibson
2023-12-21 6:53 ` [PATCH v2 02/12] icmp: Don't set "port" on destination sockaddr for ping sockets David Gibson
2023-12-21 6:53 ` [PATCH v2 03/12] icmp: Remove redundant initialisation of sendto() address David Gibson
2023-12-21 6:53 ` [PATCH v2 04/12] icmp: Don't attempt to handle "wrong direction" ping socket traffic David Gibson
2024-01-06 15:59 ` Stefano Brivio
2024-01-07 0:37 ` David Gibson
2024-01-07 14:59 ` Stefano Brivio
2023-12-21 6:53 ` [PATCH v2 05/12] icmp: Don't attempt to match host IDs to guest IDs David Gibson
2023-12-21 6:53 ` [PATCH v2 06/12] icmp: Use -1 to represent "missing" sockets David Gibson
2024-01-06 15:59 ` Stefano Brivio
2024-01-07 0:38 ` David Gibson
2023-12-21 6:53 ` [PATCH v2 07/12] icmp: Simplify socket expiry scanning David Gibson
2024-01-06 15:59 ` Stefano Brivio
2024-01-07 0:41 ` David Gibson
2023-12-21 6:53 ` [PATCH v2 08/12] icmp: Share more between IPv4 and IPv6 paths in icmp_tap_handler() David Gibson
2024-01-06 16:00 ` Stefano Brivio
2024-01-07 4:41 ` David Gibson
2023-12-21 6:53 ` [PATCH v2 09/12] icmp: Consolidate icmp_sock_handler() with icmpv6_sock_handler() David Gibson
2024-01-06 16:00 ` Stefano Brivio [this message]
2024-01-07 0:45 ` David Gibson
2023-12-21 6:53 ` [PATCH v2 10/12] icmp: Warn on receive errors from ping sockets David Gibson
2023-12-21 6:53 ` [PATCH v2 11/12] icmp: Validate packets received on " David Gibson
2023-12-21 6:53 ` [PATCH v2 12/12] icmp: Dedicated functions for starting and closing ping sequences David Gibson
2024-01-06 16:01 ` Stefano Brivio
2024-01-07 4:30 ` 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=20240106170044.0aa57f62@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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).