aboutsummaryrefslogtreecommitdiff
path: root/linux-headers/asm-arm64
diff options
context:
space:
mode:
authorJeff Cody <jcody@redhat.com>2017-11-17 22:26:16 -0500
committerJeff Cody <jcody@redhat.com>2017-11-21 11:51:18 -0500
commit4afeffc8572f40d8844b946a30c00b10da4442b1 (patch)
treef877425b21bc20e94e3560a3036ebe15be460a7a /linux-headers/asm-arm64
parent7c3d1917fd7a3de906170fa3d6d3d4c5918b1e49 (diff)
blockjob: do not allow coroutine double entry or entry-after-completion
When block_job_sleep_ns() is called, the co-routine is scheduled for future execution. If we allow the job to be re-entered prior to the scheduled time, we present a race condition in which a coroutine can be entered recursively, or even entered after the coroutine is deleted. The job->busy flag is used by blockjobs when a coroutine is busy executing. The function 'block_job_enter()' obeys the busy flag, and will not enter a coroutine if set. If we sleep a job, we need to leave the busy flag set, so that subsequent calls to block_job_enter() are prevented. This changes the prior behavior of block_job_cancel() being able to immediately wake up and cancel a job; in practice, this should not be an issue, as the coroutine sleep times are generally very small, and the cancel will occur the next time the coroutine wakes up. This fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1508708 Signed-off-by: Jeff Cody <jcody@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'linux-headers/asm-arm64')
0 files changed, 0 insertions, 0 deletions