Lines Matching defs:state
168 * for PI futexes that can mess up the state. The above argues that false-negatives
491 * No point in doing state checking here. If the waiter got here
691 * the rest of the user space mutex state is consistent, so a woken
693 * OWNER_DIED bit would create inconsistent state and malfunction
950 * Kernel cleans up PI-state, but userspace is likely hosed.
995 * task still owns the PI-state:
1044 * futex_exit_recursive - Set the tasks futex state to FUTEX_STATE_DEAD
1045 * @tsk: task to set the state on
1047 * Set the futex exit state of the task lockless. The futex waiter code
1048 * observes that state when a task is exiting and loops until the task has
1050 * waiter runs through the wait loop until the state becomes visible.
1062 /* If the state is FUTEX_STATE_EXITING then futex_exit_mutex is held */
1079 * Switch the state to FUTEX_STATE_EXITING under tsk->pi_lock.
1086 * the state change under tsk->pi_lock by a concurrent waiter must
1094 static void futex_cleanup_end(struct task_struct *tsk, int state)
1100 tsk->futex_state = state;
1103 * FUTEX_STATE_EXITING to reevaluate the state.
1111 * The state handling is done for consistency, but in the case of
1114 * futex is held on exec(), this provides at least as much state
1120 * Reset the state to FUTEX_STATE_OK. The task is alive and about