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

Manfred Spraul wrote:
> 1) I would go further and try ERESTARTSYS: ERESTARTSYS means that the
> kernel signal handler honors SA_RESTART
> 2) At least for the futex functions, it won't be as easy as replacing
> EINTR wiht ERESTARTSYS: the futex functions receive a timeout a the
> parameter, with the duration of the wait call as a parameter. You must
> use ERESTART_RESTARTBLOCK.

Whoa, not so fast.  At least the futex syscall but be interruptible by
signals.  It is crucial to return EINTR.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

Attachment: signature.asc
Description: OpenPGP digital signature

Follow-Ups:
- 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: Manfred Spraul <[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]>

Prev by Date: Re: [PATCH] ixgb: add PCI Error recovery callbacks
Next by Date: Re: SATA in 2.6.17 vs 2.6.15 (x86/ICH6)
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]