[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z3v8Yn80sAL_qjIg@mini-arch>
Date: Mon, 6 Jan 2025 07:53:06 -0800
From: Stanislav Fomichev <stfomichev@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, donald.hunter@...il.com, netdev@...r.kernel.org,
edumazet@...gle.com, pabeni@...hat.com
Subject: Re: [PATCH net-next 0/3] tools: ynl: decode link types present in
tests
On 01/04, Jakub Kicinski wrote:
> Using a kernel built for the net selftest target to run drivers/net
> tests currently fails, because the net kernel automatically spawns
> a handful of tunnel devices which YNL can't decode.
>
> Fill in those missing link types in rt_link. We need to extend subset
> support a bit for it to work.
>
> Jakub Kicinski (3):
> tools: ynl: correctly handle overrides of fields in subset
> tools: ynl: print some information about attribute we can't parse
> netlink: specs: rt_link: decode ip6tnl, vti and vti6 link attrs
>
> Documentation/netlink/specs/rt_link.yaml | 87 ++++++++++++++++++++++++
> tools/net/ynl/lib/nlspec.py | 5 +-
> tools/net/ynl/lib/ynl.py | 72 +++++++++++---------
> 3 files changed, 129 insertions(+), 35 deletions(-)
I've seen similar issues with (builtin) ip6tnl in my VMs, thanks for
fixing!
Acked-by: Stanislav Fomichev <sdf@...ichev.me>
Powered by blists - more mailing lists