Skip to content

Test sys::test_socket::test_vsock fails on Ubuntu 20.10/AMD64 beta #1310

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

Open
tommythorn opened this issue Oct 10, 2020 · 0 comments
Open

Test sys::test_socket::test_vsock fails on Ubuntu 20.10/AMD64 beta #1310

tommythorn opened this issue Oct 10, 2020 · 0 comments

Comments

@tommythorn
Copy link

tommythorn commented Oct 10, 2020

Tested nix@566e2d7dad025c9b2bef98115b584328c145675d using rust 1.47.0 (stable) on Ubuntu 20.04/AMD64 (up to date at time of testing)

cargo test hangs on test_af_alg_aead (to be file after this one). Once commented out, it fails with

failures:

---- sys::test_socket::test_vsock stdout ----
thread 'sys::test_socket::test_vsock' panicked at 'assertion failed: `(left == right)`
  left: `None`,
 right: `Some(Sys(EADDRNOTAVAIL))`', test/sys/test_socket.rs:1440:5
stefano-garzarella added a commit to stefano-garzarella/nix that referenced this issue Mar 22, 2021
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]>
bors bot added a commit that referenced this issue 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 bot added a commit that referenced this issue 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]>
asomers pushed a commit that referenced this issue Aug 14, 2021
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]>
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