From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
shuah@kernel.org, sdf@google.com, amritha.nambiar@intel.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 3/4] netlink: support all extack types in dumps
Date: Sat, 20 Apr 2024 19:00:31 -0600 [thread overview]
Message-ID: <0a67fff9-c401-40c8-acce-c285698be76a@gmail.com> (raw)
In-Reply-To: <20240420023543.3300306-4-kuba@kernel.org>
On 4/19/24 8:35 PM, Jakub Kicinski wrote:
> Note that when this commit message refers to netlink dump
> it only means the actual dumping part, the parsing / dump
> start is handled by the same code as "doit".
>
> Commit 4a19edb60d02 ("netlink: Pass extack to dump handlers")
> added support for returning extack messages from dump handlers,
> but left out other extack info, e.g. bad attribute.
>
> This used to be fine because until YNL we had little practical
> use for the machine readable attributes, and only messages were
> used in practice.
>
> YNL flips the preference 180 degrees, it's now much more useful
> to point to a bad attr with NL_SET_BAD_ATTR() than type
> an English message saying "attribute XYZ is $reason-why-bad".
>
> Support all of extack. The fact that extack only gets added if
> it fits remains unaddressed.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> net/netlink/af_netlink.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2024-04-21 1:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 2:35 [PATCH net-next 0/4] netdev: support dumping a single netdev in qstats Jakub Kicinski
2024-04-20 2:35 ` [PATCH net-next 1/4] " Jakub Kicinski
2024-04-21 0:58 ` David Ahern
2024-04-21 19:17 ` Eric Dumazet
2024-04-21 19:32 ` David Ahern
2024-04-22 13:48 ` Jakub Kicinski
2024-04-22 15:02 ` Eric Dumazet
2024-04-22 15:23 ` David Ahern
2024-04-20 2:35 ` [PATCH net-next 2/4] netlink: move extack writing helpers Jakub Kicinski
2024-04-21 0:59 ` David Ahern
2024-04-20 2:35 ` [PATCH net-next 3/4] netlink: support all extack types in dumps Jakub Kicinski
2024-04-21 1:00 ` David Ahern [this message]
2024-04-20 2:35 ` [PATCH net-next 4/4] selftests: drv-net: test dumping qstats per device Jakub Kicinski
2024-04-23 17:20 ` [PATCH net-next 0/4] netdev: support dumping a single netdev in qstats patchwork-bot+netdevbpf
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=0a67fff9-c401-40c8-acce-c285698be76a@gmail.com \
--to=dsahern@gmail.com \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.