Skip to content

common UPDATE allow custom error message#1806

Merged
michalvasko merged 1 commit into
CESNET:develfrom
jeremie6wind:devel
May 22, 2026
Merged

common UPDATE allow custom error message#1806
michalvasko merged 1 commit into
CESNET:develfrom
jeremie6wind:devel

Conversation

@jeremie6wind
Copy link
Copy Markdown
Contributor

Hello,
np_reply_err_sr checks the "(path" pattern in the error log to allocate the path variable.
When a RPC creates a custom error message without the pattern, the path variable is not allocated.
netopeer2-server can crash.
In this patch, don't use the path variable if not allocated and produce a default error on cleanup.

This is the case with some error messages from libyang-python.
BR

np_reply_err_sr checks the "(path" pattern in the error log to allocate
the path variable.
When a RPC creates a custom error message without the pattern, the path
variable is not allocated.
netopeer2-server can crash.
In this patch, don't use the path variable if not allocated and produce
a default error on cleanup.
@michalvasko
Copy link
Copy Markdown
Member

Thanks, looks okay.

@michalvasko michalvasko merged commit 4c89473 into CESNET:devel May 22, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants