Manfred Spraul wrote:
select uses ERESTARTSYS...
Sorry - I meant ERESTARTNOHAND -- Manfred - 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/
- 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]>
- Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- From: Linus Torvalds <[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: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- Next by Date: [PATCH 1/2] cpufreq: add __find_governor helper and clean up some error handling
- Previous by thread: Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- Next by thread: Re: Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
- Index(es):