Re: [PATCH v4 1/3] job: take each job's lock individually in job_txn_apply

On 02/04/2020 14:33, Max Reitz wrote: On 01.04.20 10:15, Stefan Reiter wrote: All callers of job_txn_apply hold a single job's lock, but different jobs within a transaction can have different contexts, thus we need to lock each one individually before applying the callback function. Similar to

Re: [PATCH v4 1/3] job: take each job's lock individually in job_txn_apply

On 01.04.20 10:15, Stefan Reiter wrote: > All callers of job_txn_apply hold a single job's lock, but different > jobs within a transaction can have different contexts, thus we need to > lock each one individually before applying the callback function. > > Similar to job_completed_txn_abort this

[PATCH v4 1/3] job: take each job's lock individually in job_txn_apply

All callers of job_txn_apply hold a single job's lock, but different jobs within a transaction can have different contexts, thus we need to lock each one individually before applying the callback function. Similar to job_completed_txn_abort this also requires releasing the caller's context before