feat: Add SEQPACKET socket type support for vsock #5504
+637 −16
Conversation
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
sumansaurabh requested review from Manciukic, kalyazin, pb8o and xmarcalx as code owners 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.
Summary
Implements SEQPACKET socket type support for virtio vsock to enable datagram relay use cases while preserving message boundaries.
Changes Made
Why This Change
This addresses GitHub Issue #4822 by enabling VMs to relay datagrams over vsock while maintaining packet boundaries, which is not possible with SOCK_STREAM that combines messages together. This provides a more efficient solution than implementing custom packet boundaries within stream sockets.
Testing
Verified that:
Fixes #4822
This PR was created from task: https://cloud.blackbox.ai/tasks/Nuype64zWauLUuobO0u01