Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT

Von: Ulrich Drepper <[email protected]>

> > Changing EINTR
> > to ERESTARTSYS is likely to have more impact on userland (though 
> > it still strikes me as a desirable gola to have all system calls 
> > restartable via SA_RESTART).
> 
> This is certainly a nice goal but it changes the current ABI.  

Yes, it does.

> Therefore
> it cannot be anything but an option and I don't assume we want to add so
> much cruft for just this.

There must be some framework for changing the kernel ABI over time.
We can't remain forever stuck with an ABI behaviour because 
of the development model (i.e., no 2.7/2.8).  And it probably
would not be that much code change to achieve the result?

Cheers,

Michael
-- 


"Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
-
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: Arjan van de Ven <[email protected]>

• 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: 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]>

• Prev by Date: Re: 2.6.18-rc1 bttv modprobe null pointer dereference
• Next by Date: Re: [BUG sparc64] 2.6.16-git6 broke X11 on Ultra5 with ATI Mach64
• 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]