From mboxrd@z Thu Jan 1 00:00:00 1970 From: dann frazier Date: Mon, 11 Apr 2005 21:03:06 +0000 Subject: Re: [PATCH] salinfo_decode silent exit in older 2.4s Message-Id: <1113253386.6229.24.camel@krebs.dannf> List-Id: References: <1112995423.7189.133.camel@krebs.dannf> In-Reply-To: <1112995423.7189.133.camel@krebs.dannf> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-ia64@vger.kernel.org On Mon, 2005-04-11 at 09:58 +1000, Keith Owens wrote: > On Fri, 08 Apr 2005 15:23:43 -0600, > dann frazier 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.