From: Donald Hunter <donald.hunter@gmail.com>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, jiri@resnulli.us,
jacob.e.keller@intel.com, liuhangbin@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net] tools/net/ynl: fix cli.py --subscribe feature
Date: Fri, 23 Aug 2024 11:40:20 +0100 [thread overview]
Message-ID: <m2le0n5xpn.fsf@gmail.com> (raw)
In-Reply-To: <20240823084220.258965-1-arkadiusz.kubalewski@intel.com> (Arkadiusz Kubalewski's message of "Fri, 23 Aug 2024 10:42:20 +0200")
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com> writes:
> Execution of command:
> ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml /
> --subscribe "monitor" --sleep 10
> fails with:
> Traceback (most recent call last):
> File "/root/arek/linux-dpll/./tools/net/ynl/cli.py", line 114, in <module>
> main()
> File "/root/arek/linux-dpll/./tools/net/ynl/cli.py", line 109, in main
> ynl.check_ntf()
> File "/root/arek/linux-dpll/tools/net/ynl/lib/ynl.py", line 924, in check_ntf
> op = self.rsp_by_value[nl_msg.cmd()]
> KeyError: 19
>
> The key value of 19 returned from nl_msg.cmd() is a received message
> header's nl_type, which is the id value of generic netlink family being
> addressed in the OS on subscribing. It is wrong to use it for decoding
> the notification. Expected notification message on dpll subsystem is
> DPLL_CMD_PIN_CHANGE_NTF=13, seems at that point only available as first
> byte of RAW message payload, use it to target correct op and allow further
> parsing.
>
> Fixes: "0a966d606c68" ("tools/net/ynl: Fix extack decoding for directional ops")
> Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
> ---
> tools/net/ynl/lib/ynl.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/net/ynl/lib/ynl.py b/tools/net/ynl/lib/ynl.py
> index d42c1d605969..192d6c150303 100644
> --- a/tools/net/ynl/lib/ynl.py
> +++ b/tools/net/ynl/lib/ynl.py
> @@ -921,7 +921,7 @@ class YnlFamily(SpecFamily):
> print("Netlink done while checking for ntf!?")
> continue
>
> - op = self.rsp_by_value[nl_msg.cmd()]
> + op = self.rsp_by_value[nl_msg.raw[0]]
I don't think that is the right fix. It would break notifications for
raw netlink messages. The point of NlMsg.cmd() is to abstract away where
the op id comes from. GenlMsg.cmd() returns the value unpacked from
raw[0].
The problem is that we are trying to look up the op before calling
nlproto.decode(...) but it wants to know the op to check if it has a
fixed header.
I think the fix would be to change NetlinkProtocol.decode() to perform
the op lookup, if necessary, after it has called self._decode() to
unpack the GenlMsg.
How about changing NetlinkProtocol.decode() to be:
def decode(self, ynl, nl_msg, op, ops_by_value):
msg = self._decode(nl_msg)
if op is None:
op = ops_by_value[msg.cmd()]
...
The main loop can call it like this:
nlproto.decode(self, nl_msg, op, self.rsp_by_value)
and check_ntf() can call it like this:
nlproto.decode(self, nl_msg, None, self.rsp_by_value)
> decoded = self.nlproto.decode(self, nl_msg, op)
> if decoded.cmd() not in self.async_msg_ids:
> print("Unexpected msg id done while checking for ntf", decoded)
next prev parent reply other threads:[~2024-08-23 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 8:42 [RFC PATCH net] tools/net/ynl: fix cli.py --subscribe feature Arkadiusz Kubalewski
2024-08-23 10:40 ` Donald Hunter [this message]
2024-08-23 19:31 ` Kubalewski, Arkadiusz
2024-08-23 21:22 ` Donald Hunter
2024-08-23 21:39 ` Kubalewski, Arkadiusz
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=m2le0n5xpn.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--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).