Messages in this thread | | | Date | Fri, 7 Jul 2006 05:26:36 -0400 | From | Jakub Jelinek <> | Subject | Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT |
| |
On Fri, Jul 07, 2006 at 10:02:12AM +0200, Michael Kerrisk wrote: > There have been ABI changes in the past. In the end, I assume > it's a question of relative desirability ("how broken is existing > behaviour"; or: "was that behaviour ever desirable/portable > anyway?") versus relative likelihood of breaking applications.
In futex(2) case (except FUTEX_LOCK_PI where we want it to be restartable), getting EINTR rather than the getting the syscall restarted is very desirable though and several NPTL routines rely on it.
Jakub - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |