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

ptctl(PR_SET_VMA, PR_SET_VMA_ANON_NAME, addr, len, invalid_name) returns EFAULT rather than EINVAL under QEMU #2418

Open
SteveLauC opened this issue May 25, 2024 · 8 comments

Comments

@SteveLauC
Copy link
Member

When I bump the CI Linux runner from Ubuntu 20.04 to 22.04, this test fails under QEMU for some architectures, it failed in this line:

failures:

---- test_prctl::test_set_vma_anon_name stdout ----
thread 'test_prctl::test_set_vma_anon_name' panicked at 'assertion failed: `(left == right)`
  left: `EFAULT`,
 right: `EINVAL`', test/sys/test_prctl.rs:149:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    test_prctl::test_set_vma_anon_name
@asomers
Copy link
Member

asomers commented May 25, 2024

@devnexen do you know why this test fails on Ubuntu 22.04, or can you figure out?

@devnexen
Copy link
Contributor

devnexen commented May 25, 2024

After trying, I can t make much sense of why it fails just because of a container update. Maybe update all but the cross-compiling part ?

@SteveLauC
Copy link
Member Author

Maybe update all but the cross-compiling part ?

Ubuntu 20.04 will be eof in 2025, so we have to migrate to a new version:(

@devnexen
Copy link
Contributor

would you consider trying a more advanced version just to see ? e.g. 23.04

@SteveLauC
Copy link
Member Author

SteveLauC commented May 25, 2024

would you consider trying a more advanced version just to see ? e.g. 23.04

23.04 is not available, we have 24.04, though it is still in beta. Yeah, we can give it a try

@devnexen
Copy link
Contributor

devnexen commented May 26, 2024

I barely see something else than that or ignoring the test on qemu.

@SteveLauC
Copy link
Member Author

Yeah, we can give it a try

Tried it in this commit 3ea403e, no luck, looks like we have to ignore the test?

@SteveLauC
Copy link
Member Author

Yeah, we can give it a try

Tried it in this commit 3ea403e, no luck, looks like we have to ignore the test?

Copy my comment to here:

I think we should still use Ubuntu 20.04 for that cross test as it won't harm anything until 20.04 is no longer available.

When 20.04 becomes deprecated, if this issue still exists, we will ignore it, or we can happily migrate to newer versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants