Lines Matching refs:has

42 then the kernel has no information to clean up after the held lock!
43 Userspace has no chance to clean up after the lock either - userspace is
44 the one that crashes, so it has no opportunity to clean up. Catch-22.
55 they have a robust_head set. This approach has two fundamental problems
58  - it has quite complex locking and race scenarios. The vma-based
70 calls: the kernel has to do the vma scanning unconditionally! (this is
71 because the kernel has no knowledge about how many robust futexes there
94 comparison. If the thread has registered a list, then normally the list
112 it after the list-add (or list-remove) has finished.
117 Ulrich Drepper has implemented the necessary glibc support for this new
124    over every vma (!), which the VM-based method has to do. Only a very
209 i386 and x86_64 syscalls are wired up at the moment, and Ulrich has