Lines Matching refs:that

6 what are robust futexes? To answer that, we first need to understand
7 what futexes are: normal futexes are special types of locks that in the
14 that says "there's a waiter pending", and the sys_futex(FUTEX_WAIT)
16 creates a 'futex queue' internally, so that it can later on match up the
19 value) that there were waiter(s) pending, and does the
23 completely forgets that there ever was a futex at that address. This
27 process exits prematurely while holding a pthread_mutex_t lock that is
29 pthread_mutex_t, or yum is kill -9-ed), then waiters for that lock need
30 to be notified that the last owner of the lock exited in some irregular
39 the kernel that destroys the owner task (e.g. due to a SEGFAULT), but
44 the one that crashes, so it has no opportunity to clean up. Catch-22.
47 is needed to release that futex based lock. This is one of the leading
76 This huge overhead forced the creation of CONFIG_FUTEX_ROBUST so that
77 normal kernels can turn it off, but worse than that: the overhead makes
86 robust locks that userspace is holding (maintained by glibc) - which
97 walks the list [not trusting it], and marks all locks that are owned by
114 That's all that is needed - all the rest of robust-futex cleanup is done
154 [which it currently does for !pshared robust mutexes], and that took 256
159 locks to be held at a time. Nevertheless it's nice to know that this
177 current->robust_list. [Note that in the future, if robust futexes become
217 inline function before writing up the syscalls (that function returns