clarify registered buffers iovec lifetime - #1620
Merged
Merged
Conversation
Owner
|
Commit message needs updating:
See other git commits in the tree, they all should follow this rule. Few exceptions, but at least the title (first line) of the commit should be descriptive. And if that isn't enough, add the WHY in the body. |
jiv4
force-pushed
the
man_page
branch
7 times, most recently
from
July 21, 2026 17:37
067ecf1 to
374139a
Compare
The io_uring_register_buffers* functions don't require that the memory that is backing the iovec structs stay valid for the lifetime of the ring. The caller is therefore allowed to free the iovecs in case they were allocated on the heap. Signed-off-by: Arthur Leclerc <jiv4@proton.me>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.