04.11.2021 17:53, Emanuele Giuseppe Esposito wrote:
Introduce the job locking mechanism through the whole job API,
following the comments and requirements of job-monitor (assume
lock is held) and job-driver (lock is not held).

job_{lock/unlock} is independent from_job_{lock/unlock}.

Note: at this stage, job_{lock/unlock} and job lock guard macros
are*nop*.

Signed-off-by: Emanuele Giuseppe Esposito<eespo...@redhat.com>

JOB_LOCK_GUARD / WITH_JOB_LOCK_GUARD may be used in many cases

--
Best regards,
Vladimir

Reply via email to