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
Looking at the code in liburing.h, it looks like the fields in the struct are never used. Instead io_uring_recvmsg_payload requires the msghdr passed to the setup of revcmsg_multishot to get the lengths. The same lengths that look to be in the recvmsg_out struct (at least on my kernel).
What am I missing? Seems like it would be far less error prone to use the data in the struct, and make the API calls simpler.
The text was updated successfully, but these errors were encountered:
Looking at the code in liburing.h, it looks like the fields in the struct are never used. Instead
io_uring_recvmsg_payload
requires themsghdr
passed to the setup ofrevcmsg_multishot
to get the lengths. The same lengths that look to be in therecvmsg_out
struct (at least on my kernel).What am I missing? Seems like it would be far less error prone to use the data in the struct, and make the API calls simpler.
The text was updated successfully, but these errors were encountered: