diff options
| author | Oleg Nesterov <oleg@redhat.com> | 2020-02-18 16:50:18 +0100 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2020-03-02 14:06:33 -0700 |
| commit | 6fb614920b38bbf3c1c7fcd944c6d9b5d746103d (patch) | |
| tree | 07e72f16b7e06d68a6cdfc915dcf4289e188f2bf /arch/um | |
| parent | 3684f24653534c71c7dc9f44d7281a838f4e4979 (diff) | |
| download | linux-6fb614920b38bbf3c1c7fcd944c6d9b5d746103d.tar.bz2 | |
task_work_run: don't take ->pi_lock unconditionally
As Peter pointed out, task_work() can avoid ->pi_lock and cmpxchg()
if task->task_works == NULL && !PF_EXITING.
And in fact the only reason why task_work_run() needs ->pi_lock is
the possible race with task_work_cancel(), we can optimize this code
and make the locking more clear.
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'arch/um')
0 files changed, 0 insertions, 0 deletions