You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since commit c83a84afbef (fix segfault when passed blobmsg attr is NULL) parsing an empty message, like when "{}" is passed as argument to ubus call, return an error, it was working just fine before this commit.
This mean that ubus methods with only optional arguments need to check that blob_len() doesn't return 0, which is annoying and might break various existing programs. At the very least blobmsg_parse() shouldn't error out when the blob length is 0, but it might also make sense to accept a NULL message as well, just don't segfault.
The text was updated successfully, but these errors were encountered:
AlbanBedel:
Since commit c83a84afbef (fix segfault when passed blobmsg attr is NULL) parsing an empty message, like when "{}" is passed as argument to
ubus call
, return an error, it was working just fine before this commit.This mean that ubus methods with only optional arguments need to check that blob_len() doesn't return 0, which is annoying and might break various existing programs. At the very least blobmsg_parse() shouldn't error out when the blob length is 0, but it might also make sense to accept a NULL message as well, just don't segfault.
The text was updated successfully, but these errors were encountered: