Lines Matching refs:up

16 creates a 'futex queue' internally, so that it can later on match up the
20 sys_futex(FUTEX_WAKE) syscall to wake them up.  Once all waiters have
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.
72 are to be cleaned up, because a robust futex might have been registered
90 locks to be cleaned up?
98 this thread with the FUTEX_OWNER_DIED bit, and wakes up one waiter (if
109 kernel to clean up if the thread dies after acquiring the lock, but just
192 and wakes up the next futex waiter (if any). User-space does the rest of
209 i386 and x86_64 syscalls are wired up at the moment, and Ulrich has
217 inline function before writing up the syscalls (that function returns