All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Remy D. Farley" <one-d-wide@protonmail.com>
Cc: Donald Hunter <donald.hunter@gmail.com>,
	netdev@vger.kernel.org, fw@strlen.de
Subject: Re: [PATCH] doc/netlink: Fix typos in operation attributes
Date: Mon, 15 Sep 2025 18:26:36 -0700	[thread overview]
Message-ID: <20250915182636.7284c0ad@kernel.org> (raw)
In-Reply-To: <20250913140515.1132886-1-one-d-wide@protonmail.com>

On Sat, 13 Sep 2025 14:05:28 +0000 Remy D. Farley wrote:
> I'm trying to generate Rust bindings for netlink using the yaml spec.
> 
> It looks like there's a typo in conntrack spec: attribute set conntrack-attrs
> defines attributes "counters-{orig,reply}" (plural), while get operation
> references "counter-{orig,reply}" (singular). The latter should be fixed, as it
> denotes multiple counters (packet and byte). The corresonding C define is
> CTA_COUNTERS_ORIG.
> 
> Also, dump request references "nfgen-family" attribute, which neither exists in
> conntrack-attrs attrset nor ctattr_type enum. There's member of nfgenmsg struct
> with the same name, which is where family value is actually taken from.
> 
> > static int ctnetlink_dump_exp_ct(struct net *net, struct sock *ctnl,
> >                struct sk_buff *skb,
> >                const struct nlmsghdr *nlh,
> >                const struct nlattr * const cda[],
> >                struct netlink_ext_ack *extack)
> > {
> >   int err;
> >   struct nfgenmsg *nfmsg = nlmsg_data(nlh);
> >   u_int8_t u3 = nfmsg->nfgen_family;  
>                          ^^^^^^^^^^^^

cc: fw@strlen.de
Fixes: 23fc9311a526 ("netlink: specs: add conntrack dump and stats dump support")
Reviewed-by: Jakub Kicinski <kuba@kernel.org>

>  Documentation/netlink/specs/conntrack.yaml | 9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/netlink/specs/conntrack.yaml b/Documentation/netlink/specs/conntrack.yaml
> index c6832633a..591e22a2e 100644
> --- a/Documentation/netlink/specs/conntrack.yaml
> +++ b/Documentation/netlink/specs/conntrack.yaml
> @@ -575,8 +575,8 @@ operations:
>              - nat-dst
>              - timeout
>              - mark
> -            - counter-orig
> -            - counter-reply
> +            - counters-orig
> +            - counters-reply
>              - use
>              - id
>              - nat-dst
> @@ -591,7 +591,6 @@ operations:
>          request:
>            value: 0x101
>            attributes:
> -            - nfgen-family
>              - mark
>              - filter
>              - status
> @@ -608,8 +607,8 @@ operations:
>              - nat-dst
>              - timeout
>              - mark
> -            - counter-orig
> -            - counter-reply
> +            - counters-orig
> +            - counters-reply
>              - use
>              - id
>              - nat-dst


  reply	other threads:[~2025-09-16  1:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-13 14:05 [PATCH] doc/netlink: Fix typos in operation attributes Remy D. Farley
2025-09-16  1:26 ` Jakub Kicinski [this message]
2025-09-16 23:40 ` 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=20250915182636.7284c0ad@kernel.org \
    --to=kuba@kernel.org \
    --cc=donald.hunter@gmail.com \
    --cc=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    --cc=one-d-wide@protonmail.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.
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.