Manfred Spraul wrote: > Is it necessary that the futex syscall ignores SA_RESTART? You might break some incorrectly written code this wait. sem_wait(), one example, directly exposes the EINTR error to program. That behavior would change from what it is today, better or worse depends on the situation. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
Attachment:
signature.asc
Description: OpenPGP digital signature
- 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: 2.6.17-mm6
- Next by Date: Re: + edac-new-opteron-athlon64-memory-controller-driver.patch added to -mm tree
- 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):