Re: [PATCH] salinfo_decode silent exit in older 2.4s

[Keith Owens <kaos@sgi.com>]

On Mon, 11 Apr 2005 15:03:06 -0600, 
dann frazier <dannf@hp.com> wrote:
>On Mon, 2005-04-11 at 09:58 +1000, Keith Owens wrote:
>> On Fri, 08 Apr 2005 15:23:43 -0600, 
>> dann frazier <dannf@hp.com> wrote:
>> >I was playing with salinfo_decode on an older kernel (2.4.21 era) and it
>> >would normally die silently right after exec.
>> >
>> >This no longer happens because of a semantic difference that occurred in
>> >later 2.4 kernels.  Older 2.4s would return -EINTR when they wanted
>> >userspace to try again, while current 2.4s use -ERESTARTSYS.  (The
>> >surrounding code is also somewhat different, but it looks like the idea
>> >is the same).
>> 
>> ERESTARTSYS should never be seen by user space code.  The kernel should
>> either restart the current syscall or convert the code to EINTR before
>> returning to user space.  If you are seeing ERESTARTSYS in user space
>> then it is a kernel bug.
>
>Right, that's not the problem I'm seeing.  The problem I'm seeing is
>that older kernels return -EINTR, which causes salinfo_decode to
>silently exit.

I coded that exit on the assumption that the only reason salinfo_decode
would get -EINTR is from a signal.  salinfo_decode 0.7 does not have
alarms, so the only signal should be from an external event, i.e. when
the user wants to shut it down.  Before changing the behaviour, can you
find out why -EINTR is being returned in the first place.  IOW, what
event is causing -EINTR to be returned.