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 [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: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
    • From: Ulrich Drepper <[email protected]>

• References:
  • 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: 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: Ulrich Drepper <[email protected]>
  • 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: Ulrich Drepper <[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: Arjan van de Ven <[email protected]>
  • Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
    • From: "Michael Kerrisk" <[email protected]>

• Prev by Date: Re: linux-2.6.17-mm6: strange kobject message
• Next by Date: Re: linux-2.6.17-mm6: strange kobject message
• 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):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]