From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756623AbYKTRBW (ORCPT ); Thu, 20 Nov 2008 12:01:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753543AbYKTRBL (ORCPT ); Thu, 20 Nov 2008 12:01:11 -0500 Received: from mx1.suse.de ([195.135.220.2]:54876 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752950AbYKTRBK (ORCPT ); Thu, 20 Nov 2008 12:01:10 -0500 Date: Thu, 20 Nov 2008 18:01:08 +0100 Message-ID: From: Takashi Iwai To: Arjan van de Ven Cc: linux-kernel@vger.kernel.org, Luc Verhaegen , Egbert Eich Subject: Re: vm86 segfaults with NX bit In-Reply-To: <20081120085844.6f158e08@infradead.org> References: <20081120085844.6f158e08@infradead.org> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.3 (x86_64-suse-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Thu, 20 Nov 2008 08:58:44 -0800, Arjan van de Ven wrote: > > On Thu, 20 Nov 2008 16:39:06 +0100 > Takashi Iwai wrote: > > > Hi, > > > > X guys reported that VESA driver segfaults in vm86 mode with a kernel > > with CONFIG_X86_PAE, and it turned to be the NX bit. See Novell > > bugzilla #443440: > > https://bugzilla.novell.com/show_bug.cgi?id=443440 > > > > I can confirm that the latest 2.6.28-rc still causes the same problem, > > and it disappears when booted with noexec=off option. > > > > Also, when NX bit is reset for the first 1MB (or smaller) in > > do_sys_vm86(), it also works as expected. But I have little clue > > where to restore the bit again. > > > > Any good suggestions / solutions? > > > > did the code that mapped this memory setup use PROT_EXEC ? A good question... Luc, Egbert, how does VESA driver handle it? Takashi