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
The docs say that these functions may return null, but they're not null-checked in the locations above (the usage of CMSG_NXTHDR for initializing next_message is, however). The code is dereferencing the results here and dereferencing a null pointer is UB: it should null-check these.
The text was updated successfully, but these errors were encountered:
As far as I understand they'll only return null if there's not enough space.
The code tries to calculate and allocate the required space, so it should never happen.
But assertions have been added in #8, and has now been released in 0.2.7 and 0.3.0.
And there was a bug in the space calculation, which is also fixed in those versions.
uds/src/ancillary.rs
Line 128 in d8cefa3
uds/src/ancillary.rs
Line 137 in d8cefa3
uds/src/ancillary.rs
Line 333 in d8cefa3
uds/src/ancillary.rs
Line 358 in d8cefa3
uds/src/ancillary.rs
Line 129 in d8cefa3
The docs say that these functions may return null, but they're not null-checked in the locations above (the usage of
CMSG_NXTHDR
for initializingnext_message
is, however). The code is dereferencing the results here and dereferencing a null pointer is UB: it should null-check these.The text was updated successfully, but these errors were encountered: