From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Anshu Kumari <anskuma@redhat.com>,
passt-dev@passt.top, v@njh.eu, lvivier@redhat.com
Subject: Re: [PATCH v3] tap, tcp, udp: Use rate-limited logging
Date: Thu, 16 Apr 2026 11:24:04 +1000 [thread overview]
Message-ID: <aeA6NE-4C14n6lh3@zatzit> (raw)
In-Reply-To: <20260415213836.418df481@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]
On Wed, Apr 15, 2026 at 09:38:36PM +0200, Stefano Brivio wrote:
> On Mon, 13 Apr 2026 16:25:52 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > On Fri, Apr 10, 2026 at 04:07:37PM +0530, Anshu Kumari 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>
> >
> > Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> >
> > > ---
> > > v3:
> > > - Promote flow allocation failures to err_ratelimit from
> > > warn_ratelimit.
> >
> > Nit: doesn't affect the validity of the patch itself, but I'd consider
> > "promotion" in this context as going from a less severe to more severe
> > error level. So going from 'err' to 'warn' is a demotion, not a
> > promotion.
>
> Wait but this is now going _from_ 'warn' _to_ 'err', so it's indeed a
> promotion, isn't it?
Oh, sorry, my mistake. I misread "to x from y" as "from x to y".
--
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 --]
next prev parent reply other threads:[~2026-04-16 1:24 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 [this message]
2026-04-15 19:38 ` 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=aeA6NE-4C14n6lh3@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=anskuma@redhat.com \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
--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).