linux-kernel - Re: Bug: retry of clone() on Alpha can result in zeroed process thread pointer

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <53D947E4.7020305@twiddle.net>
Date:	Wed, 30 Jul 2014 09:30:44 -1000
From:	Richard Henderson <rth@...ddle.net>
To:	Michael Cree <mcree@...on.net.nz>, linux-alpha@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Bug: retry of clone() on Alpha can result in zeroed process thread
 pointer

Ok, I think I've actually found it this time.  It's here:

> 281		childregs->r20 = 1;	/* OSF/1 has some strange fork() semantics.  */
> 282		regs->r20 = 0;

We need to delay this r20 silliness until after restarts or something.  Or just
kill it -- it's not like glibc uses this return value.


r~
--
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/