On Fri, Jan 08, 2010 at 05:28:58PM -0500, John David Anglin wrote: > > On Fri, Jan 08, 2010 at 04:44:51PM -0500, Carlos O'Donell wrote: > > > > > > > > However, I think Dave is on to something with the > > > > > > ...kernel issue. > > > > > > We might have *several* outstanding bugs :-) > > > > > > > Hrm. We discussed this on IRC a while ago, I can't remember what we > > decided was the best approach... there's probably many many dragons > > here. > > > > I wonder what would break if we set any EAGAIN returns to EWOULDBLOCK in > > the exit path. > > That seems reversed. x86_64 translates the system's EWOULDBLOCK error > into EAGAIN in sysdeps/unix/x86_64/sysdep.S. However, don't know if this > impacts the futex and sem_wait checks. Yeah, you're right. regards, Kyle -- 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
