aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/futex.c
diff options
context:
space:
mode:
Diffstat (limited to 'kernel/futex.c')
-rw-r--r--kernel/futex.c13
1 files changed, 3 insertions, 10 deletions
diff --git a/kernel/futex.c b/kernel/futex.c
index 381125a9f1e0..2aa216e5b594 100644
--- a/kernel/futex.c
+++ b/kernel/futex.c
@@ -2060,7 +2060,7 @@ pi_faulted:
2060 * 2060 *
2061 * Returns 2061 * Returns
2062 * 0 - no early wakeup detected 2062 * 0 - no early wakeup detected
2063 * <0 - -ETIMEDOUT or -ERESTARTSYS (FIXME: or ERESTARTNOINTR?) 2063 * <0 - -ETIMEDOUT or -ERESTARTNOINTR
2064 */ 2064 */
2065static inline 2065static inline
2066int handle_early_requeue_pi_wakeup(struct futex_hash_bucket *hb, 2066int handle_early_requeue_pi_wakeup(struct futex_hash_bucket *hb,
@@ -2087,15 +2087,8 @@ int handle_early_requeue_pi_wakeup(struct futex_hash_bucket *hb,
2087 2087
2088 if (timeout && !timeout->task) 2088 if (timeout && !timeout->task)
2089 ret = -ETIMEDOUT; 2089 ret = -ETIMEDOUT;
2090 else { 2090 else
2091 /* 2091 ret = -ERESTARTNOINTR;
2092 * We expect signal_pending(current), but another
2093 * thread may have handled it for us already.
2094 */
2095 /* FIXME: ERESTARTSYS or ERESTARTNOINTR? Do we care if
2096 * the user specified SA_RESTART or not? */
2097 ret = -ERESTARTSYS;
2098 }
2099 } 2092 }
2100 return ret; 2093 return ret;
2101} 2094}