| commit | 13726123ba916dd8ead23156a61db8d2c8bd42e8 | |
| author | Kevin Wolf <kwolf@redhat.com> | |
| Fri, 3 May 2019 17:17:43 +0000 (3 19:17 +0200) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Fri, 10 May 2019 14:45:40 +0000 (10 16:45 +0200) | ||
| tree | df31043b6efe4244e1219f5a504c1f5510a9d61e | treesnapshot (tar.gz zip) |
| parent | 4d231a384c5d72491e6ddc8006d6be929ca6c609 | commitdiff |
blockjob: Fix coroutine thread after AioContext change
Commit 463e0be10 ('blockjob: add AioContext attached callback') tried to
make block jobs robust against AioContext changes of their main node,
but it never made sure that the job coroutine actually runs in the new
thread.
Instead of waking up the job coroutine in whatever thread it ran before,
let's always pass the AioContext where it should be running now.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Commit 463e0be10 ('blockjob: add AioContext attached callback') tried to
make block jobs robust against AioContext changes of their main node,
but it never made sure that the job coroutine actually runs in the new
thread.
Instead of waking up the job coroutine in whatever thread it ran before,
let's always pass the AioContext where it should be running now.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| job.c | diffblobblamehistory |