From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/4] RFC: Improvements to flow specific logging
Date: Wed, 17 Jun 2026 01:08:55 +0200 (CEST) [thread overview]
Message-ID: <20260617010854.01e36b3a@elisabeth> (raw)
In-Reply-To: <20260609023226.86058-1-david@gibson.dropbear.id.au>
On Tue, 9 Jun 2026 12:32:22 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> 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.
Unless I'm missing something, I don't see 4/4 as particularly
problematic. It's a set of rather mechanical changes where the compiler
would tell us if we got something wrong, I guess?
> Still, current drafted posted for consideration.
>
> David Gibson (4):
> flow: Regularise flow specific logging helpers
> flow: Include flow details with higher priority log messages
> flow: Safer errno handling in flowside_connect() callers
> flow, treewide: Promote priority of selected flow-linked messages
>
> flow.c | 107 +++++++-------
> flow.h | 72 +++++-----
> icmp.c | 27 ++--
> icmp.h | 3 +-
> migrate.c | 27 ++--
> migrate.h | 8 +-
> passt.c | 8 +-
> tcp.c | 381 ++++++++++++++++++++++++++++---------------------
> tcp.h | 5 +-
> tcp_buf.c | 78 +++++-----
> tcp_buf.h | 8 +-
> tcp_conn.h | 8 +-
> tcp_internal.h | 27 ++--
> tcp_splice.c | 59 +++++---
> tcp_splice.h | 3 +-
> tcp_vu.c | 42 +++---
> tcp_vu.h | 6 +-
> udp.c | 48 ++++---
> udp_flow.c | 22 +--
> 19 files changed, 535 insertions(+), 404 deletions(-)
--
Stefano
prev parent reply other threads:[~2026-06-16 23:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 2:32 David Gibson
2026-06-09 2:32 ` [PATCH 1/4] flow: Regularise flow specific logging helpers David Gibson
2026-06-16 23:09 ` Stefano Brivio
2026-06-17 2:03 ` David Gibson
2026-06-09 2:32 ` [PATCH 2/4] flow: Include flow details with higher priority log messages David Gibson
2026-06-16 23:09 ` Stefano Brivio
2026-06-17 2:15 ` David Gibson
2026-06-17 5:22 ` Stefano Brivio
2026-06-09 2:32 ` [PATCH 3/4] flow: Safer errno handling in flowside_connect() callers David Gibson
2026-06-16 23:09 ` Stefano Brivio
2026-06-17 2:25 ` David Gibson
2026-06-09 2:32 ` [PATCH 4/4] flow, treewide: Promote priority of selected flow-linked messages David Gibson
2026-06-16 23:09 ` Stefano Brivio
2026-06-17 3:08 ` David Gibson
2026-06-16 23:08 ` Stefano Brivio [this message]
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=20260617010854.01e36b3a@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).