diff options
| author | Jeff Cody | 2018-08-21 18:26:19 +0200 |
|---|---|---|
| committer | Jeff Cody | 2018-08-21 20:59:30 +0200 |
| commit | e321c0597c7590499bacab239d7f86e257f96bcd (patch) | |
| tree | 887df1322c2db6108238ebc246c1e6824f79edfa /hw/i2c | |
| parent | Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-3.1-20180821' into... (diff) | |
| download | qemu-e321c0597c7590499bacab239d7f86e257f96bcd.tar.gz qemu-e321c0597c7590499bacab239d7f86e257f96bcd.tar.xz qemu-e321c0597c7590499bacab239d7f86e257f96bcd.zip | |
block: for jobs, do not clear user_paused until after the resume
The function job_cancel_async() will always cause an assert for blockjob
user resume. We set job->user_paused to false, and then call
job->driver->user_resume(). In the case of blockjobs, this is the
block_job_user_resume() function.
In that function, we assert that job.user_paused is set to true.
Unfortunately, right before calling this function, it has explicitly
been set to false.
The fix is pretty simple: set job->user_paused to false only after the
job user_resume() function has been called.
Reviewed-by: John Snow <jsnow@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Jeff Cody <jcody@redhat.com>
Message-id: bb183b77d8f2dd6bd67b8da559a90ac1e74b2052.1534868459.git.jcody@redhat.com
Signed-off-by: Jeff Cody <jcody@redhat.com>
Diffstat (limited to 'hw/i2c')
0 files changed, 0 insertions, 0 deletions