| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 1 Aug 2014 09:00:23 +1200 From: Michael Cree <mcree@...on.net.nz> To: Richard Henderson <rth@...ddle.net> Cc: linux-kernel@...r.kernel.org, linux-alpha@...r.kernel.org Subject: Re: [PATCH 1/2] alpha: Remove "strange" OSF/1 fork semantics 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 <mcree@...on.net.nz> > Signed-off-by: Richard Henderson <rth@...ddle.net> 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 <mcree@...on.net.nz> Cheers Michael. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists