From: Hangbin Liu <hangbin.liu@linux.dev>
To: sashiko-reviews@lists.linux.dev
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 5/6] netlink: specs: rt-route: describe lwt BPF program options
Date: Fri, 18 Sep 2026 15:32:59 +0800 [thread overview]
Message-ID: <aqzpK1H8Pib6bVcY@fedora> (raw)
In-Reply-To: <20260918063655.EA1DC1F00893@smtp.kernel.org>
On Fri, Sep 18, 2026 at 06:36:55AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] netlink: specs: build failure due to missing header in lwt-bpf-prog
> --
>
> commit 73e4e6736fda4554b1e22b6360a42d9d2e02b4dc
> Author: Hangbin Liu <liuhangbin@kylinos.cn>
>
> netlink: specs: rt-route: describe lwt BPF program options
>
> This replaces binary BPF attributes with a nested lwt-bpf-prog attribute
> to support lwt bpf prog options.
>
> > diff --git a/Documentation/netlink/specs/rt-route.yaml b/Documentation/netlink/specs/rt-route.yaml
> > index 6030d7cb8d0d1..5e9537f7dfad4 100644
> > --- a/Documentation/netlink/specs/rt-route.yaml
> > +++ b/Documentation/netlink/specs/rt-route.yaml
>
> [ ... ]
>
> > @@ -610,6 +614,16 @@ attribute-sets:
> > -
> > name: hwid
> > type: u8
> > + -
> > + name: lwt-bpf-prog
> > + name-prefix: lwt-bpf-prog-
> > + attributes:
>
> [Severity: Low]
> Will this cause a build failure in the generated YNL tools due to a missing
> header?
>
> Because the header property is omitted for the lwt-bpf-prog attribute set,
> the YNL code generator will automatically output the C enumerators
> LWT_BPF_PROG_FD and LWT_BPF_PROG_NAME in its generated header.
>
> Other attribute sets in this spec correctly specify header: linux/lwtunnel.h,
> which causes the generated YNL header to globally include it. Since the
> kernel header linux/lwtunnel.h already defines LWT_BPF_PROG_FD and
> LWT_BPF_PROG_NAME, compiling the userspace YNL tools will result in a fatal
> redefinition error.
>
> Should a header property mapping to linux/lwtunnel.h be added here?
Yes, I will do it.
next prev parent reply other threads:[~2026-09-18 7:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 6:35 [PATCH net-next 0/6] netlink: add lwtunnel encap sub-message support to rt-route Hangbin Liu
2026-09-17 6:35 ` [PATCH net-next 1/6] net: lwtunnel: change encap fill order Hangbin Liu
2026-09-18 6:36 ` sashiko-bot
2026-09-21 6:38 ` netdev-bot+sashiko
2026-09-17 6:35 ` [PATCH net-next 2/6] tools: ynl: convert enum selector to string for sub-message parsing Hangbin Liu
2026-09-18 6:36 ` sashiko-bot
2026-09-18 9:29 ` Hangbin Liu
2026-09-21 6:38 ` netdev-bot+sashiko
2026-09-17 6:35 ` [PATCH net-next 3/6] netlink: specs: rt-route: add lwtunnel encap sub-message support Hangbin Liu
2026-09-18 6:36 ` sashiko-bot
2026-09-18 7:51 ` Hangbin Liu
2026-09-21 6:38 ` netdev-bot+sashiko
2026-09-17 6:35 ` [PATCH net-next 4/6] netlink: specs: rt-route: describe lwtunnel IP options Hangbin Liu
2026-09-18 6:36 ` sashiko-bot
2026-09-18 8:02 ` Hangbin Liu
2026-09-21 6:38 ` netdev-bot+sashiko
2026-09-21 9:26 ` Hangbin Liu
2026-09-17 6:35 ` [PATCH net-next 5/6] netlink: specs: rt-route: describe lwt BPF program options Hangbin Liu
2026-09-18 6:36 ` sashiko-bot
2026-09-18 7:32 ` Hangbin Liu [this message]
2026-09-21 6:38 ` netdev-bot+sashiko
2026-09-21 9:46 ` Hangbin Liu
2026-09-17 6:35 ` [PATCH net-next 6/6] netlink: specs: rt-route: describe seg6-local actions, counters and flavors Hangbin Liu
2026-09-21 6:38 ` netdev-bot+sashiko
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=aqzpK1H8Pib6bVcY@fedora \
--to=hangbin.liu@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.