Re: Syscall restarted with the clobbered 5th argument

[Paul M. <le...@li...>]

On Sun, Jun 17, 2007 at 07:20:15AM +0900, Kaz Kojima wrote:
> I'm working on the latest GNU libc with the 2.6.22-rc4 kernel and
> I've found a few kernel problems.  This is the first one.
> 
> We use R0 as the 5th argument of syscall.  When the syscall restarts
> after signal handling, we should restore the old value of R0.
> The attached patch does it.  Without this patch, I've experienced random
> failures in the situation which signals are issued frequently.
> 
Applied, thanks. I'll add this to the 2.6.22 queue.