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 00/11] RFC: ICMP reworks preliminary to flow table integration
Date: Tue, 16 Jan 2024 16:16:07 +1100 [thread overview]
Message-ID: <20240116051618.2746103-1-david@gibson.dropbear.id.au> (raw)
As with TCP, it turns out that there are a bunch of clean ups and
reworks to the ICMP code which will make integration with the flow
table easier, even before introducing a non-trivial version of the
flow table itself.
Based on the flow based dispatch/allocation, and bind/addressing
cleanup series.
Changes since v2:
* Rebased on current main and revised flow dispatch series
* Standardise on the name 'id_sock' instead of 'id_map' for pointers
to specific entries in the id_map
* Avoid confusing usage of the word "sequence" to mean a flow of ping
packets as opposed to the ping sequence number.
* Use packet_get() rather than explicit comparisons to validate
packet lengths
Changes since v1:
* Rebased on newer version of flow dispatch & allocation series
* Added 12/12 splitting out close and new sequence functions
David Gibson (11):
icmp: Don't set "port" on destination sockaddr for ping sockets
icmp: Remove redundant initialisation of sendto() address
icmp: Don't attempt to handle "wrong direction" ping socket traffic
icmp: Don't attempt to match host IDs to guest IDs
icmp: Use -1 to represent "missing" sockets
icmp: Simplify socket expiry scanning
icmp: Share more between IPv4 and IPv6 paths in icmp_tap_handler()
icmp: Consolidate icmp_sock_handler() with icmpv6_sock_handler()
icmp: Warn on receive errors from ping sockets
icmp: Validate packets received on ping sockets
icmp: Dedicated functions for starting and closing ping sequences
icmp.c | 329 ++++++++++++++++++++++++++++----------------------------
icmp.h | 5 +-
passt.c | 4 +-
3 files changed, 166 insertions(+), 172 deletions(-)
--
2.43.0
next reply other threads:[~2024-01-16 5:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 5:16 David Gibson [this message]
2024-01-16 5:16 ` [PATCH v3 01/11] icmp: Don't set "port" on destination sockaddr for ping sockets David Gibson
2024-01-16 5:16 ` [PATCH v3 02/11] icmp: Remove redundant initialisation of sendto() address David Gibson
2024-01-16 5:16 ` [PATCH v3 03/11] icmp: Don't attempt to handle "wrong direction" ping socket traffic David Gibson
2024-01-16 5:16 ` [PATCH v3 04/11] icmp: Don't attempt to match host IDs to guest IDs David Gibson
2024-01-16 5:16 ` [PATCH v3 05/11] icmp: Use -1 to represent "missing" sockets David Gibson
2024-01-16 5:16 ` [PATCH v3 06/11] icmp: Simplify socket expiry scanning David Gibson
2024-01-16 5:16 ` [PATCH v3 07/11] icmp: Share more between IPv4 and IPv6 paths in icmp_tap_handler() David Gibson
2024-01-16 5:16 ` [PATCH v3 08/11] icmp: Consolidate icmp_sock_handler() with icmpv6_sock_handler() David Gibson
2024-01-16 5:16 ` [PATCH v3 09/11] icmp: Warn on receive errors from ping sockets David Gibson
2024-01-16 5:16 ` [PATCH v3 10/11] icmp: Validate packets received on " David Gibson
2024-01-16 5:16 ` [PATCH v3 11/11] icmp: Dedicated functions for starting and closing ping sequences David Gibson
2024-01-23 0:39 ` [PATCH v3 00/11] RFC: ICMP reworks preliminary to flow table integration 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=20240116051618.2746103-1-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).