Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262945AbUCXAlg (ORCPT ); Tue, 23 Mar 2004 19:41:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262954AbUCXAlg (ORCPT ); Tue, 23 Mar 2004 19:41:36 -0500 Received: from mx1.redhat.com ([66.187.233.31]:43732 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S262945AbUCXAlc (ORCPT ); Tue, 23 Mar 2004 19:41:32 -0500 Date: Tue, 23 Mar 2004 19:41:10 -0500 (EST) From: Ingo Molnar X-X-Sender: mingo@devserv.devel.redhat.com To: Andrew Morton cc: Kurt Garloff , linux-kernel@vger.kernel.org Subject: Re: Non-Exec stack patches In-Reply-To: <20040323164104.11d79f32.akpm@osdl.org> Message-ID: References: <20040323231256.GP4677@tpkurt.garloff.de> <20040323154937.1f0dc500.akpm@osdl.org> <20040324002149.GT4677@tpkurt.garloff.de> <20040323164104.11d79f32.akpm@osdl.org> 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: 551 Lines: 15 On Tue, 23 Mar 2004, Andrew Morton wrote: > Now, what should the kernel do if the executable requests > EXSTACK_DISABLE_X but the kernel cannot do that? Is it not a bit > misleading/dangerous to permit the executable to run anyway? it's not really a problem. We already ignore the !X bit on x86. Ingo - 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/