task_work: Replace spin_unlock_wait() with lock/unlock pair
authorOleg Nesterov <oleg@redhat.com>
Fri, 30 Jun 2017 20:13:59 +0000 (13:13 -0700)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Tue, 25 Jul 2017 17:08:58 +0000 (10:08 -0700)
commitf274f1e72d7171c80c8c790040e47a23a74796b6
tree1e69960fc748abd6fd3454a9a782851f200ff92f
parent3ef0c7a730de0bae03d86c19570af764fa3c4445
task_work: Replace spin_unlock_wait() with lock/unlock pair

There is no agreed-upon definition of spin_unlock_wait()'s semantics,
and it appears that all callers could do just as well with a lock/unlock
pair.  This commit therefore replaces the spin_unlock_wait() call in
task_work_run() with a spin_lock_irq() and a spin_unlock_irq() aruond
the cmpxchg() dequeue loop.  This should be safe from a performance
perspective because ->pi_lock is local to the task and because calls to
the other side of the race, task_work_cancel(), should be rare.

Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
kernel/task_work.c