futex: Correct futex_wait_requeue_pi() commentary

 * We call schedule in futex_wait_queue_me() when we enqueue and return there

 * via the following:

 * 1) wakeup on uaddr2 after an atomic lock acquisition by futex_requeue()

 * 2) wakeup on uaddr2 after a requeue and subsequent unlock

 * 3) signal (before or after requeue)

 * 4) timeout (before or after requeue)

 * 2) wakeup on uaddr2 after a requeue

 * 3) signal

 * 4) timeout

 *

 * If 3, we setup a restart_block with futex_wait_requeue_pi() as the function.

 * If 3, cleanup and return -ERESTARTNOINTR.

 *

 * If 2, we may then block on trying to take the rt_mutex and return via:

 * 5) successful lock

 * 7) timeout

 * 8) other lock acquisition failure

 *

 * If 6, we setup a restart_block with futex_lock_pi() as the function.

 * If 6, return -EWOULDBLOCK (restarting the syscall would do the same).

 *

 * If 4 or 7, we cleanup and return with -ETIMEDOUT.

 *

			rt_mutex_unlock(pi_mutex);

	} else if (ret == -EINTR) {

		/*

		 * We've already been requeued, but we have no way to

		 * restart by calling futex_lock_pi() directly. We

		 * could restart the syscall, but that will look at

		 * the user space value and return right away. So we

		 * drop back with EWOULDBLOCK to tell user space that

		 * "val" has been changed. That's the same what the

		 * restart of the syscall would do in

		 * futex_wait_setup().

		 * We've already been requeued, but cannot restart by calling

		 * futex_lock_pi() directly. We could restart this syscall, but

		 * it would detect that the user space "val" changed and return

		 * -EWOULDBLOCK.  Save the overhead of the restart and return

		 * -EWOULDBLOCK directly.

		 */

		ret = -EWOULDBLOCK;

	}