Commit a2d4c71d authored Jun 27, 2012 by Al Viro

deal with task_work callbacks adding more work



It doesn't matter on normal return to userland path (we'll recheck the
NOTIFY_RESUME flag anyway), but in case of exit_task_work() we'll
need that as soon as we get callbacks capable of triggering more
task_work_add().

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

parent ed3e694d

kernel/task_work.c

+14 −12

Original line number	Diff line number	Diff line
		@@ -60,6 +60,7 @@ void task_work_run(void)
		struct task_struct *task = current;
		struct callback_head p, q;

		while (1) {
		raw_spin_lock_irq(&task->pi_lock);
		p = task->task_works;
		task->task_works = NULL;
		@@ -76,3 +77,4 @@ void task_work_run(void)
		q = p;
		}
		}
		}

Admin message