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

The global lock is too restrictive #812

Open
poncovka opened this issue Nov 4, 2019 · 0 comments
Open

The global lock is too restrictive #812

poncovka opened this issue Nov 4, 2019 · 0 comments

Comments

@poncovka
Copy link
Contributor

poncovka commented Nov 4, 2019

We would like to be able to work with different copies of Blivet at the same time, but currently it is not possible, because Blivet uses one global lock for every object it owns. It doesn't cause any problems at this moment, because Anaconda is designed to wait for all the long-term storage-related jobs to be done before we do anything else with the storage. However, it affects the usability of our DBus Storage module. We call reset on a new copy of Blivet in a separate thread, but DBus calls can be blocked by the global lock until the reset is finished even though they use a different copy of Blivet at that moment.

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