tools: ynl-gen: always construct struct ynl_req_state
struct ynl_req_state carries reply-related info from generated code into generic YNL code. While we don't need reply info to execute a request without a reply, we still need to pass in the struct, because it's also where we get the pointer to struct ynl_sock from. Passing NULL results in crashes if kernel returns an error or an unexpected reply. Fixes: dc0956c9 ("tools: ynl-gen: move the response reading logic into YNL") Link: https://lore.kernel.org/r/20231126225858.2144136-1-kuba@kernel.org Signed-off-by:Jakub Kicinski <kuba@kernel.org>
Showing
- tools/net/ynl/generated/devlink-user.c 58 additions, 29 deletionstools/net/ynl/generated/devlink-user.c
- tools/net/ynl/generated/ethtool-user.c 34 additions, 17 deletionstools/net/ynl/generated/ethtool-user.c
- tools/net/ynl/generated/fou-user.c 4 additions, 2 deletionstools/net/ynl/generated/fou-user.c
- tools/net/ynl/generated/handshake-user.c 2 additions, 1 deletiontools/net/ynl/generated/handshake-user.c
- tools/net/ynl/ynl-gen-c.py 4 additions, 6 deletionstools/net/ynl/ynl-gen-c.py
Loading
Please register or sign in to comment