All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, Luc Verhaegen <lverhaegen@suse.de>,
	Egbert Eich <eich@suse.de>
Subject: Re: vm86 segfaults with NX bit
Date: Thu, 20 Nov 2008 18:01:08 +0100	[thread overview]
Message-ID: <s5h3ahm9vsb.wl%tiwai@suse.de> (raw)
In-Reply-To: <20081120085844.6f158e08@infradead.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 <tiwai@suse.de> 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

  reply	other threads:[~2008-11-20 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 15:39 vm86 segfaults with NX bit Takashi Iwai
2008-11-20 15:58 ` Alan Cox
2008-11-20 16:00   ` Takashi Iwai
2008-11-20 16:05     ` Takashi Iwai
2008-11-20 16:58 ` Arjan van de Ven
2008-11-20 17:01   ` Takashi Iwai [this message]
2008-11-20 17:05     ` Takashi Iwai
2008-11-20 21:24       ` H. Peter Anvin
2008-11-21 11:38         ` Takashi Iwai
2008-11-21 17:42     ` Egbert Eich
2008-11-22 10:20       ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5h3ahm9vsb.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=arjan@infradead.org \
    --cc=eich@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lverhaegen@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.