public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Anshu Kumari <anskuma@redhat.com>
Cc: passt-dev@passt.top, david@gibson.dropbear.id.au, v@njh.eu,
	lvivier@redhat.com
Subject: Re: [PATCH v3] tap, tcp, udp: Use rate-limited logging
Date: Wed, 15 Apr 2026 21:38:43 +0200 (CEST)	[thread overview]
Message-ID: <20260415213842.7142e5d4@elisabeth> (raw)
In-Reply-To: <20260410103737.1642986-1-anskuma@redhat.com>

On Fri, 10 Apr 2026 16:07:37 +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, promote dropped datagram messages to warn level, and
> rate-limit the unrecoverable socket error message.
> 
> In udp_flow.c, promote flow allocation failures to err_ratelimit.
> 
> Link: https://bugs.passt.top/show_bug.cgi?id=134
> Signed-off-by: Anshu Kumari <anskuma@redhat.com>
> ---
>  v3:
>    - Promote flow allocation failures to err_ratelimit from
>      warn_ratelimit.
>    - Fix remaining alignment issues.
>    - Cc Volker

Applied.

-- 
Stefano


      parent reply	other threads:[~2026-04-15 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 10:37 Anshu Kumari
2026-04-13  6:25 ` David Gibson
2026-04-15 19:38   ` Stefano Brivio
2026-04-16  1:24     ` David Gibson
2026-04-15 19:38 ` 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=20260415213842.7142e5d4@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=anskuma@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=v@njh.eu \
    /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).