linux-kernel - RE: [tip:x86/urgent] x86/entry: Restore traditional SYSENTER calling convention

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: <E6AF1AFDEA62A94A97508F458CBDD47F3D9CBEB5@SHSMSX101.ccr.corp.intel.com>
Date:	Tue, 5 Jan 2016 06:51:04 +0000
From:	"Zhuo, Qiuxu" <qiuxu.zhuo@...el.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>
CC:	Andy Lutomirski <luto@...capital.net>,
	"Shi, Mingwei" <mingwei.shi@...el.com>,
	"Fu, Borun" <borun.fu@...el.com>,
	"Gross, Mark" <mark.gross@...el.com>,
	Andrew Lutomirski <luto@...nel.org>,
	"Su, Tao" <tao.su@...el.com>, Borislav Petkov <bp@...en8.de>,
	Ingo Molnar <mingo@...nel.org>,
	Brian Gerst <brgerst@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	"Wang, Frank" <frank.wang@...el.com>,
	"linux-tip-commits@...r.kernel.org" 
	<linux-tip-commits@...r.kernel.org>
Subject: RE: [tip:x86/urgent] x86/entry: Restore traditional SYSENTER
 calling convention

Hi Linus and Andy,

  We did test in our side with v4.4-rc8 + Andy's vDSO v2 patches + Android M (bionic libc using sysenter) ==> Device can boot up successfully

  Other tests were:
  - Android L (bionic libc using int80) + v4.4-rc8 ==> Device can boot up successfully
  - Android L (bionic libc using int80) + v4.4-rc8 + Andy's v2 patches ==> Device can boot up successfully
  - Android M (bionic libc using sysenter) + v4.4-rc8 ==> Device can NOT boot up successfully
  - Android M (bionic libc using sysenter) + v4.4-rc8 + Andy's v2 patches ==> Device can boot up successfully

   Thanks!
BR
qiuxu

-----Original Message-----
From: linus971@...il.com [mailto:linus971@...il.com] On Behalf Of Linus Torvalds
Sent: Tuesday, January 5, 2016 3:28 AM
To: H. Peter Anvin
Cc: Andy Lutomirski; Shi, Mingwei; Fu, Borun; Gross, Mark; Andrew Lutomirski; Su, Tao; Borislav Petkov; Ingo Molnar; Brian Gerst; linux-kernel@...r.kernel.org; Zhuo, Qiuxu; Thomas Gleixner; Denys Vlasenko; Wang, Frank; linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86/entry: Restore traditional SYSENTER calling convention

On Mon, Jan 4, 2016 at 10:48 AM, H. Peter Anvin <hpa@...or.com> wrote:
>
> Linus has frequently stated that if it is something that is critical 
> enough for stable, it is critical enough for final.  Linus will decide 
> if an additional -rc is needed for that reason.

So it would have been good to have it in an -rc, but at the same time I'm not particularly worried about this one.

It's not like it's complicated, and I'm assuming it got tested and passed all our current test-cases (which are much more complete than anything we've ever had historically).

                     Linus