public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Anshu Kumari <anskuma@redhat.com>,
	passt-dev@passt.top, lvivier@redhat.com
Subject: Re: [PATCH v1 2/2] tap, tcp, udp: Use rate-limited logging
Date: Tue, 7 Apr 2026 10:46:56 +1000	[thread overview]
Message-ID: <adRUAGTuR-9imnmY@zatzit> (raw)
In-Reply-To: <20260406101247.3d9b3086@elisabeth>

[-- Attachment #1: Type: text/plain, Size: 2195 bytes --]

On Mon, Apr 06, 2026 at 10:12:48AM +0200, Stefano Brivio wrote:
> On Wed,  1 Apr 2026 23:59:10 +0530
> Anshu Kumari <anskuma@redhat.com> wrote:
> 
> > Now that rate-limited logging macros are available, promote several
> > debug messages to higher severity levels.  These messages were
> > previously kept at debug to prevent guests from flooding host
> > logs, but with rate limiting they can safely be made visible in
> > normal operation.
> > 
> > In tap.c, refactor tap4_is_fragment() to use warn_ratelimit() instead
> > of its ad-hoc rate limiting, and promote the guest MAC address change
> > message to info level.
> > 
> > In tcp.c, promote the invalid TCP SYN endpoint message to warn level.
> > 
> > In udp.c and udp_flow.c, promote flow allocation failures and dropped
> > datagram messages to warn level, and rate-limit the unrecoverable
> > socket error message.
> > 
> > Link: https://bugs.passt.top/show_bug.cgi?id=134
> 
> By the way of this ticket, I forgot to mention that as it came up after
> a discussion on a series by Volker (Volker Diels-Grabsch <v@njh.eu>),
> it would be nice to Cc: him on the next version of this patch.
> 
> > Signed-off-by: Anshu Kumari <anskuma@redhat.com>
> > ---
> > 
> > - Inside udp.c
> > - David: should this be changed to warn_ratelimit? I am not sure about it
> >   debug("%s error on UDP socket %i: %s",
> >     str_ee_origin(ee), s, strerror_(ee->ee_errno));
> 
> I had a closer look, and it looks like we're hitting that part for any
> error reported via ICMP that can be associated to a given UDP socket, so
> I would say it's part of our regular networking operation, and we
> should keep it as debug().

Thinking about this again, I agree.  Looking at this another way, the
error is already being reported at the right level: as an ICMP message
to the guest.  At the passt level this might be useful for debugging,
hence debug() but doesn't represent anything out of the ordinary or
worrying.

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-04-07  0:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 18:29 Anshu Kumari
2026-04-02 15:10 ` Laurent Vivier
2026-04-02 15:33   ` Stefano Brivio
2026-04-06  8:12 ` Stefano Brivio
2026-04-07  0:46   ` David Gibson [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=adRUAGTuR-9imnmY@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=anskuma@redhat.com \
    --cc=lvivier@redhat.com \
    --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).