Thread (6 messages) 6 messages, 2 authors, 2014-07-31

Re: [PATCH 1/2] alpha: Remove "strange" OSF/1 fork semantics

From: Michael Cree <hidden>
Date: 2014-07-31 21:01:11
Also in: lkml

On Wed, Jul 30, 2014 at 11:42:31AM -1000, Richard Henderson wrote:
The assignment to regs->r20 kills the original tls_val input
to the clone syscall, which means that clone can no longer be
restarted with the original inputs.

We could, perhaps, retain this result for true fork, but OSF/1
compatibility is no longer important.  Note that glibc has never
used the r20 result value, instead always testing r0 vs 0 to
determine the child/parent status.

This failure can be seen in the glibc nptl/tst-eintr* tests.

Reported-by: Michael Cree <redacted>
Signed-off-by: Richard Henderson <redacted>
The glibc nptl/tst-eintr3 test now works successfully on the SMP
system with the patched kernel.

In addition builds of openjdk-6 or openjdk-7 use to always fail
because javac would randomly lock up at some point.  A test build of
openjdk-6 has just built successfully to completion with the patched
kernel.

I am not able to test whether OSF/1 compatibility is adversely
affected.

Tested-by: Michael Cree <redacted>

Cheers
Michael.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help