Go to file
Thomas Lamprecht b36e8acc31 alloc track: acquire BS AIO context during dropping
ran into this when live-restoring a backup configured for IO-threads,
got the good ol':
> qemu: qemu_mutex_unlock_impl: Operation not permitted
error.

Checking out the history of the related bdrv_backup_top_drop(*bs)
method, we can see that it used to do the AIO context acquiring too,
but in the backup path this was problematic and was changed to be
higher up in the call path in a upstream series from Stefan[0].

That said, this is a completely different code path and it is safe to
do so here. We always run from the main threads's AIO context here
and we call it only indirectly once, guarded by checking for
`s->drop_state == DropNone` and set `s->drop_state = DropRequested`
shortly before we schedule the track_drop() in a bh.

[0]: https://lists.gnu.org/archive/html/qemu-devel/2020-03/msg09139.html

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2021-04-06 16:27:48 +02:00
debian alloc track: acquire BS AIO context during dropping 2021-04-06 16:27:48 +02:00
keycodemapdb bump version to 3.0.0-1 2018-09-07 14:52:23 +02:00
qemu@553032db17 Update to QEMU 5.2 2021-02-12 10:20:01 +01:00
.gitmodules import stable-4 build files 2017-04-05 11:39:09 +02:00
backup.txt correct link to vma spec to new repository url 2020-01-14 11:18:52 +01:00
Makefile Update to QEMU 5.2 2021-02-12 10:20:01 +01:00
vma_spec.txt import stable-4 build files 2017-04-05 11:39:09 +02:00