linux-kernel - [PATCH 0/2] minor cleanups to EFLAGS initialisation in ret_from

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-next>] [day] [month] [year] [list]

Message-ID: <1314782541.28989.37.camel@zakaz.uk.xensource.com>
Date:	Wed, 31 Aug 2011 10:22:21 +0100
From:	Ian Campbell <Ian.Campbell@...rix.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
CC:	Cyrill Gorcunov <gorcunov@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Pekka Enberg <penberg@...nel.org>,
	Andi Kleen <ak@...ux.intel.com>
Subject: [PATCH 0/2] minor cleanups to EFLAGS initialisation in
 ret_from_fork

This fell off my radar but Cyrill kindly reminded me so here is a repost
of my short cleanup to remove the kernel_eflags variable from 64 bit and
to converge the ret_from_fork paths on 32 and 64 bit slightly.

This is unchanged from the last posting except I have rebased to current
tip/master and retested (it boots successfully on both 32 and 64 bit).

As previously discussed since the original posting I have switched to
converging on the 64 bit variant rather than the 32 bit variant.
Although I believe both variants are strictly speaking correct and
equivalent the 64 bit version seems to be more obviously so.

Ian.

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