On Thu, 6 Jul 2006, Manfred Spraul wrote: > > Is it necessary that the futex syscall ignores SA_RESTART? Very possibly. That was definitely the case for "select()" long ago. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- From: "Michael Kerrisk" <[email protected]>
- Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- From: Manfred Spraul <[email protected]>
- Re: Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- References:
- Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- From: Michael Kerrisk <[email protected]>
- Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- From: Manfred Spraul <[email protected]>
- Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- From: "Michael Kerrisk" <[email protected]>
- Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- From: Manfred Spraul <[email protected]>
- Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- From: Ulrich Drepper <[email protected]>
- Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- From: Manfred Spraul <[email protected]>
- Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- Prev by Date: Re: + edac-new-opteron-athlon64-memory-controller-driver.patch added to -mm tree
- Next by Date: Re: swsusp / suspend2 reliability
- Previous by thread: Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- Next by thread: Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- Index(es):
 |