Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269515AbUIZLjh (ORCPT ); Sun, 26 Sep 2004 07:39:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269516AbUIZLje (ORCPT ); Sun, 26 Sep 2004 07:39:34 -0400 Received: from zero.aec.at ([193.170.194.10]:41483 "EHLO zero.aec.at") by vger.kernel.org with ESMTP id S269515AbUIZLjI (ORCPT ); Sun, 26 Sep 2004 07:39:08 -0400 To: Ingo Molnar Cc: Jan Beulich , linux-kernel@vger.kernel.org, Andrew Morton , arjanv@redhat.com Subject: Re: i386 entry.S problems References: <2HZ5Q-3MU-17@gated-at.bofh.it> <2HZSa-4nZ-63@gated-at.bofh.it> <2IFew-HK-9@gated-at.bofh.it> From: Andi Kleen Date: Sun, 26 Sep 2004 13:38:45 +0200 In-Reply-To: <2IFew-HK-9@gated-at.bofh.it> (Ingo Molnar's message of "Sun, 26 Sep 2004 13:20:08 +0200") Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 715 Lines: 21 Ingo Molnar writes: >> >> I wonder why we still have the lcall7/lcall27 entry points in the >> kernel; nothing can legitemately use them and in the last few years >> they have only caused a few security issues. Can I ask why you didn't >> just remove this code from the kernel ? > > patch below (against BK-curr) zaps the orphaned lcall7/lcall27 code. I did this for x86-64 long ago :-) You can zap the default LDT handling in ldt.c then too. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/