From: Donald Hunter <donald.hunter@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
edumazet@google.com, pabeni@redhat.com, andrew+netdev@lunn.ch,
horms@kernel.org, jstancek@redhat.com
Subject: Re: [PATCH net-next] tools: ynl: default to --process-unknown in installed mode
Date: Fri, 11 Jul 2025 12:11:35 +0100 [thread overview]
Message-ID: <m2a55b56e0.fsf@gmail.com> (raw)
In-Reply-To: <20250710175115.3465217-1-kuba@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> We default to raising an exception when unknown attrs are found
> to make sure those are noticed during development.
> When YNL CLI is "installed" and used by sysadmins erroring out
> is not going to be helpful. It's far more likely the user space
> is older than the kernel in that case, than that some attr is
> misdefined or missing.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Good call.
Reviewed-by: Donald Hunter <donald.hunter@gmail.com>
> ---
> CC: donald.hunter@gmail.com
> CC: jstancek@redhat.com
> ---
> tools/net/ynl/pyynl/cli.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/net/ynl/pyynl/cli.py b/tools/net/ynl/pyynl/cli.py
> index 33ccc5c1843b..8c192e900bd3 100755
> --- a/tools/net/ynl/pyynl/cli.py
> +++ b/tools/net/ynl/pyynl/cli.py
> @@ -113,6 +113,8 @@ relative_schema_dir='../../../../Documentation/netlink'
> spec = f"{spec_dir()}/{args.family}.yaml"
> if args.schema is None and spec.startswith(sys_schema_dir):
> args.schema = '' # disable schema validation when installed
> + if args.process_unknown is None:
> + args.process_unknown = True
> else:
> spec = args.spec
> if not os.path.isfile(spec):
next prev parent reply other threads:[~2025-07-11 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 17:51 [PATCH net-next] tools: ynl: default to --process-unknown in installed mode Jakub Kicinski
2025-07-11 11:11 ` Donald Hunter [this message]
2025-07-13 22:10 ` 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=m2a55b56e0.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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.
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 NNTP newsgroup(s).