From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756522Ab2AUABy (ORCPT ); Fri, 20 Jan 2012 19:01:54 -0500 Received: from terminus.zytor.com ([198.137.202.10]:43432 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754027Ab2AUABv (ORCPT ); Fri, 20 Jan 2012 19:01:51 -0500 References: <20120116183730.GB21112@redhat.com> <4F1731C1.4050007@zytor.com> <4F1733DF.7040905@zytor.com> <4F1737C9.3070905@zytor.com> <4F173F48.2070604@zytor.com> <4F176605.5020101@zytor.com> <4F19EDAF.2000109@zytor.com> User-Agent: K-9 Mail for Android In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: Compat 32-bit syscall entry from 64-bit task!? From: "hpanvin@gmail.com" Date: Fri, 20 Jan 2012 15:58:21 -0800 To: Roland McGrath , Indan Zupancic CC: Denys Vlasenko , Linus Torvalds , Andi Kleen , Jamie Lokier , Andrew Lutomirski , Oleg Nesterov , Will Drewry , linux-kernel@vger.kernel.org, keescook@chromium.org, john.johansen@canonical.com, serge.hallyn@canonical.com, coreyb@linux.vnet.ibm.com, pmoore@redhat.com, eparis@redhat.com, djm@mindrot.org, segoon@openwall.com, rostedt@goodmis.org, jmorris@namei.org, scarybeasts@gmail.com, avi@redhat.com, penberg@cs.helsinki.fi, viro@zeniv.linux.org.uk, mingo@elte.hu, akpm@linux-foundation.org, khilman@ti.com, borislav.petkov@amd.com, amwang@redhat.com, ak@linux.intel.com, eric.dumazet@gmail.com, gregkh@suse.de, dhowells@redhat.com, daniel.lezcano@free.fr, linux-fsdevel@vger.kernel.org, linux-security-module@vger.kernel.org, olofj@chromium.org, mhalcrow@google.com, dlaor@redhat.com Message-ID: <529e70ab-8a37-478a-8ba1-af5f5b9156e4@email.android.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Linus claims it does break. Roland McGrath wrote: >On Fri, Jan 20, 2012 at 3:49 PM, Indan Zupancic wrote: >> It's a lot easier for existing code to add an extra cs check than to >use > >The issue is whether showing fictitious high bits of %cs as set will >break >existing applications (debuggers, etc.) that look at it and think that >it's >nothing but the hardware state zero-extended, as it is today. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.