Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

io_uring_recvmsg_out fields never used by liburing? #1230

Open
TwoClocks opened this issue Sep 16, 2024 · 0 comments
Open

io_uring_recvmsg_out fields never used by liburing? #1230

TwoClocks opened this issue Sep 16, 2024 · 0 comments

Comments

@TwoClocks
Copy link

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.

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

No branches or pull requests

1 participant