> On Fri, Jan 8, 2010 at 4:44 PM, Carlos O'Donell <carlos@xxxxxxxxxxxxxxxx> w= > rote: > > On Fri, Jan 8, 2010 at 4:18 PM, Helge Deller <deller@xxxxxx> wrote: > >>> I now think this probably is a glibc bug. =A0The 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 fut= > ex > >> syscall against EWOULDBLOCK. > >> Since on parisc - in contrast to all other architectures - we have > >> EWOULDBLOCK!=3DEAGAIN, 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. Hacking glibc to check for both does not fix the testcase ;( > > However, I think Dave is on to something with the > > ...kernel issue. > > We might have *several* outstanding bugs :-) Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- 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
