core-admin/qubes/storage
3hhh 3db5e9f8bf
Revert "storage/callback: do not run sync code async"
This reverts commit 287a4a0429.

As Marek correctly pointed out, sync functions cannot be run async against one another even if run inside an async function
(the python interpreter will remain active until the next yield and that's at the end of the sync func / inside the async function).
--> So there's no need for a lock.

I still cannot protect against assumptions made by sync code authors about blocking the Qubes OS main loop. Those will be broken.

Moreover the code of this commit was botched anyway.
2020-07-28 18:42:02 +02:00
..
__init__.py Adjust code for possibly coroutine Volume.export() and Volume.export_end() 2020-07-08 12:50:10 +02:00
callback.json.example storage/callback: async Volume.export() & added Volume.export_end() 2020-07-16 17:02:19 +02:00
callback.py Revert "storage/callback: do not run sync code async" 2020-07-28 18:42:02 +02:00
file.py Adjust code for possibly coroutine Volume.export() and Volume.export_end() 2020-07-08 12:50:10 +02:00
kernels.py storage: clean up __init__() of Pool() and subclasses 2020-06-22 14:03:21 +00:00
lvm.py storage/lvm: make the "hack" work with CallbackPool instances 2020-07-16 14:31:04 +02:00
README.md Merge remote-tracking branch 'marmarek/master' into core3-devel 2016-03-03 01:13:51 +01:00
reflink.py Adjust code for possibly coroutine Volume.export() and Volume.export_end() 2020-07-08 12:50:10 +02:00

WNI File storage

Before v3.1 there existed a draft wni storage. You can find it in the git history

(it was in /core/storage directory, now gone)