From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752702Ab2AWCOr (ORCPT ); Sun, 22 Jan 2012 21:14:47 -0500 Received: from smarthost1.greenhost.nl ([195.190.28.78]:49605 "EHLO smarthost1.greenhost.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752607Ab2AWCOo (ORCPT ); Sun, 22 Jan 2012 21:14:44 -0500 Message-ID: <4beb01a79f7566eb356dfae622791b11.squirrel@webmail.greenhost.nl> In-Reply-To: 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> Date: Mon, 23 Jan 2012 03:14:13 +0100 Subject: Re: Compat 32-bit syscall entry from 64-bit task!? From: "Indan Zupancic" To: "Roland McGrath" Cc: "H. Peter Anvin" , "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 User-Agent: SquirrelMail/1.4.22 MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: 1.4 X-Scan-Signature: a07cf4f22b7e0347d98fbeb4081a69be Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, January 21, 2012 00:55, 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. Argh, sorry, I meant eflags. I even checked how many bits are free in eflags and still wrote 'cs'. Greetings, Indan