From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Jon Maloy <jmaloy@redhat.com>, dgibson@redhat.com, passt-dev@passt.top
Subject: Re: [PATCH v14 01/10] netlink: add subscription on changes in NDP/ARP table
Date: Mon, 20 Oct 2025 11:17:23 +1100 [thread overview]
Message-ID: <aPV_kzNS5YuB6BKh@zatzit> (raw)
In-Reply-To: <20251019120730.01c2cf4f@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Sun, Oct 19, 2025 at 12:07:30PM +0200, Stefano Brivio wrote:
> On Tue, 14 Oct 2025 22:55:12 -0400
> Jon Maloy <jmaloy@redhat.com> wrote:
[snip]
> > + warn("neigh_msg_read() failed, error %i", errmsg->error);
>
> But neigh_msg_read() isn't a function name (it's nl_neigh_msg_read()).
> To avoid that, if you really need the function name, I'd suggest %s and
> __func__.
>
> However, here, I don't think you can say that the function failed. It's
> just that we got an error from netlink. The function didn't do almost
> anything. Maybe just "netlink error on neighbour notifier: ..."?
I didn't catch this when I reviewed, but I think it's probably best to
avoid function names in messages above debug() level. Rationale:
debug() and trace() messages are aimed in large part towards
developers, and can have whatever information is useful to them,
warn(), err() and die() are aimed at users to whom function names are
meaningless.
--
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:[~2025-10-20 0:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 2:55 [PATCH v14 00/10] Use true MAC address of LAN local remote hosts Jon Maloy
2025-10-15 2:55 ` [PATCH v14 01/10] netlink: add subscription on changes in NDP/ARP table Jon Maloy
2025-10-17 2:36 ` David Gibson
2025-10-19 10:07 ` Stefano Brivio
2025-10-20 0:17 ` David Gibson [this message]
2025-10-15 2:55 ` [PATCH v14 02/10] passt: add no_map_gw flag to struct ctx Jon Maloy
2025-10-19 10:07 ` Stefano Brivio
2025-10-15 2:55 ` [PATCH v14 03/10] fwd: Add cache table for ARP/NDP contents Jon Maloy
2025-10-17 3:05 ` David Gibson
2025-10-17 18:49 ` Jon Maloy
2025-10-20 0:06 ` David Gibson
2025-10-20 10:00 ` Jon Maloy
2025-10-22 1:20 ` David Gibson
2025-10-19 10:07 ` Stefano Brivio
2025-10-15 2:55 ` [PATCH v14 04/10] arp/ndp: respond with true MAC address of LAN local remote hosts Jon Maloy
2025-10-17 3:06 ` David Gibson
2025-10-15 2:55 ` [PATCH v14 05/10] arp/ndp: send ARP announcement / unsolicited NA when neigbour entry added Jon Maloy
2025-10-17 3:08 ` David Gibson
2025-10-19 10:08 ` Stefano Brivio
2025-10-15 2:55 ` [PATCH v14 06/10] flow: add MAC address of LAN local remote hosts to flow Jon Maloy
2025-10-15 2:55 ` [PATCH v14 07/10] udp: forward external source MAC address through tap interface Jon Maloy
2025-10-15 2:55 ` [PATCH v14 08/10] tcp: " Jon Maloy
2025-10-15 2:55 ` [PATCH v14 09/10] tap: change signature of function tap_push_l2h() Jon Maloy
2025-10-15 2:55 ` [PATCH v14 10/10] icmp: let icmp use mac address from flowside structure Jon Maloy
2025-10-19 10:08 ` 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=aPV_kzNS5YuB6BKh@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=dgibson@redhat.com \
--cc=jmaloy@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).