public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v2 0/6] Improvements to flow specific logging
Date: Wed, 17 Jun 2026 13:11:16 +1000	[thread overview]
Message-ID: <20260617031122.2086827-1-david@gibson.dropbear.id.au> (raw)

While working on podman bug 23739, I found some deficiences in how and
when we report various socket errors related to specific flows.  Here
are some preliminary patches to improve that.

I think patches 1..3 are pretty straightforward and safe.  4/4 I think
is a good idea in principle - promoting the priority of a number of
messages now that we have ratelimiting.  However, plumbing 'now' all
the places we need it resuls in a *lot* of churn, so we might want to
postpone or split it up.

Still, current drafted posted for consideration.

v2:
 * Added patch 2/6 At Stefano's suggestion
 * Simplified the errno Handling fix at Stefano's suggestion
 * Added patch 6/6 which I noticed while revising 5/6.
 * Made a handful of minor corrections based on feedback.

David Gibson (6):
  flow: Regularise flow specific logging helpers
  flow: Indent flow details messages
  flow: Include flow details with higher priority log messages
  flow, udp: Fix errno handling in udp_flow_sock()
  flow, treewide: Promote priority of selected flow-linked messages
  udp: Improve messages for errors getting errors

 flow.c         | 103 ++++++-------
 flow.h         |  72 ++++-----
 icmp.c         |  27 ++--
 icmp.h         |   3 +-
 migrate.c      |  27 ++--
 migrate.h      |   8 +-
 passt.c        |   8 +-
 tcp.c          | 387 ++++++++++++++++++++++++++++---------------------
 tcp.h          |   5 +-
 tcp_buf.c      |  67 +++++----
 tcp_buf.h      |   7 +-
 tcp_conn.h     |   8 +-
 tcp_internal.h |  27 ++--
 tcp_splice.c   |  59 +++++---
 tcp_splice.h   |   3 +-
 tcp_vu.c       |  31 ++--
 tcp_vu.h       |   5 +-
 udp.c          |  61 +++++---
 udp_flow.c     |  18 ++-
 19 files changed, 528 insertions(+), 398 deletions(-)

-- 
2.54.0


             reply	other threads:[~2026-06-17  3:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17  3:11 David Gibson [this message]
2026-06-17  3:11 ` [PATCH v2 1/6] flow: Regularise flow specific logging helpers David Gibson
2026-06-17  3:11 ` [PATCH v2 2/6] flow: Indent flow details messages David Gibson
2026-06-17  3:11 ` [PATCH v2 3/6] flow: Include flow details with higher priority log messages David Gibson
2026-06-17  3:11 ` [PATCH v2 4/6] flow, udp: Fix errno handling in udp_flow_sock() David Gibson
2026-06-17  3:11 ` [PATCH v2 5/6] flow, treewide: Promote priority of selected flow-linked messages David Gibson
2026-06-17  5:23   ` Stefano Brivio
2026-06-17  3:11 ` [PATCH v2 6/6] udp: Improve messages for errors getting errors 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=20260617031122.2086827-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).