On Fri, Jan 8, 2010 at 4:44 PM, Carlos O'Donell <carlos@xxxxxxxxxxxxxxxx> wrote: > On Fri, Jan 8, 2010 at 4:18 PM, Helge Deller <deller@xxxxxx> wrote: >>> I now think this probably is a glibc bug. The kernel uses this value >>> when the CLONE_PARENT_SETTID flag is passed. >> >> >> Maybe we have a futex problem in glibc on hppa? >> In glibc nptl/pthread_mutex_trylock.c we check the return value of a futex >> syscall against EWOULDBLOCK. >> Since on parisc - in contrast to all other architectures - we have >> EWOULDBLOCK!=EAGAIN, we maybe missed a check? > > That's a bug. There are several kernel paths that could return EAGAIN > *or* EWOULDBLOCK via the FUTEX_TRYLOCK_PI futex operation. > > However, I think Dave is on to something with the ...kernel issue. We might have *several* outstanding bugs :-) Cheers, Carlos. -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
