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

Execute each restrict_self() test in a dedicated thread #46

Merged
merged 1 commit into from
Aug 31, 2023

Conversation

l0kod
Copy link
Member

@l0kod l0kod commented Aug 31, 2023

Ensures restrict_self() is called on a dedicated thread to avoid inconsistent tests.

The visible effect (with Rust 1.63) was for restrict_self() to sometime return E2BIG because of too many stacked domains. This inconsistency was related to the number of tests (i.e. the number of successful restrict_self() calls), but not directly related to their content.

Ensures restrict_self() is called on a dedicated thread to avoid
inconsistent tests.

The visible effect (with Rust 1.63) was for restrict_self() to sometime
return E2BIG because of too many stacked domains. This inconsistency was
related to the number of tests (i.e. the number of successful
restrict_self() calls), but not directly related to their content.

Signed-off-by: Mickaël Salaün <mic@digikod.net>
@l0kod l0kod merged commit dbd4105 into landlock-lsm:main Aug 31, 2023
12 checks passed
@l0kod l0kod deleted the isolate-tests-with-restrict-self branch August 31, 2023 12:47
@l0kod l0kod mentioned this pull request Feb 21, 2024
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.

None yet

1 participant