Skip to content

Fix test_vsock failure on VMADDR_CID_LOCAL testing and re-enable it #1407

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

Merged
merged 2 commits into from
Mar 23, 2021

Conversation

stefano-garzarella
Copy link
Contributor

Starting from Linux 5.6, VMADDR_CID_LOCAL is supported to do local communication (loopback device).

Before Linux 5.6 it was called VMADDR_CID_RESERVED and was not supported, so we could expect an EADDRNOTAVAIL, but now this address is supported and handled by the 'vsock_loopback' kernel module loaded automatically if no other vsock transports are loaded.

Issue #1310
Issue #1403

Signed-off-by: Stefano Garzarella [email protected]

Starting from Linux 5.6, VMADDR_CID_LOCAL is supported to do local
communication (loopback device).

Before Linux 5.6 it was called VMADDR_CID_RESERVED and was not
supported, so we could expect an EADDRNOTAVAIL, but now this address
is supported and handled by the 'vsock_loopback' kernel module loaded
automatically if no other vsock transports are loaded.

Issue nix-rust#1310
Issue nix-rust#1403

Signed-off-by: Stefano Garzarella <[email protected]>
This reverts commit c0783e7.

Now the test should work correctly, so we can re-enable it.

Signed-off-by: Stefano Garzarella <[email protected]>
Copy link
Member

@asomers asomers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the quick fix!

bors r+

bors bot added a commit that referenced this pull request Mar 23, 2021
1407: Fix test_vsock failure on VMADDR_CID_LOCAL testing and re-enable it r=asomers a=stefano-garzarella

Starting from Linux 5.6, `VMADDR_CID_LOCAL` is supported to do local communication (loopback device).

Before Linux 5.6 it was called `VMADDR_CID_RESERVED` and was not supported, so we could expect an `EADDRNOTAVAIL`, but now this address is supported and handled by the 'vsock_loopback' kernel module loaded automatically if no other vsock transports are loaded.

Issue #1310
Issue #1403

Signed-off-by: Stefano Garzarella <[email protected]>

Co-authored-by: Stefano Garzarella <[email protected]>
@bors
Copy link
Contributor

bors bot commented Mar 23, 2021

Build failed:

@asomers
Copy link
Member

asomers commented Mar 23, 2021

bors retry

@bors bors bot merged commit 5e491c8 into nix-rust:master Mar 23, 2021
@stefano-garzarella stefano-garzarella deleted the fix-vsock-test branch March 23, 2021 09:03
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

Successfully merging this pull request may close these issues.

3 participants