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

EVCs modified without holding lock, may lead to race conditions #512

Open
Ktmi opened this issue Sep 23, 2024 · 0 comments
Open

EVCs modified without holding lock, may lead to race conditions #512

Ktmi opened this issue Sep 23, 2024 · 0 comments
Assignees
Labels
2024.2 Kytos-ng 2024.2 epic_mef_eline_consistency_v2 consistency

Comments

@Ktmi
Copy link

Ktmi commented Sep 23, 2024

In several of the functions used to update or modify EVCs, the state of the EVC is modified without holding the lock. For example, an EVC can be in the middle of checking if it is valid for consistency check and before performing the consistency check be updated by the rest endpoint, which can then change the base assumption the consistency check was started under. This doesn't just apply to the aforemention example, but is a problem spread throughout mef_eline.

@Ktmi Ktmi added 2024.2 Kytos-ng 2024.2 epic_mef_eline_consistency_v2 consistency labels Sep 23, 2024
@Ktmi Ktmi self-assigned this Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2024.2 Kytos-ng 2024.2 epic_mef_eline_consistency_v2 consistency
Projects
None yet
Development

No branches or pull requests

1 participant