From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Kyle McMartin <kyle@ubuntu.com>
Cc: John Richard Moser <nigelenki@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: noexec=on doesn't work
Date: Mon, 11 Dec 2006 20:53:57 +0100 [thread overview]
Message-ID: <457DB755.1000100@tremplin-utc.net> (raw)
In-Reply-To: <20061209200323.GA21514@athena.road.mcmartin.ca>
12/09/2006 09:03 PM, Kyle McMartin wrote/a écrit:
> On Sat, Dec 09, 2006 at 02:34:47PM -0500, John Richard Moser wrote:
>> I have filed this as a distro bug with Ubuntu; it may be their issue, I
>> haven't dug deep enough to find out. I am posting this here to disperse
>> the information breadth-first instead of depth-first, which will shorten
>> the bug's life cycle if it turns out to be an upstream bug.
>>
>
> NX requires the 64-bit page table entries (ie, PAE) which requires
> CONFIG_HIGHMEM64G.
Somehow there is a problem: a user can explicitly put "noexec=on" and it
will be silently ignored if the kernel doesn't have PAE support. I guess
that currently no message is written because "noexec=on" is the
_default_. Still, it would be fair to the user who added "noexec=on" on
its command line that if it is not respected, either because the
hardware doesn't support it or because the kernel doesn't support it, we
display a warning saying it's hopeless.
I'll send a patch if it seems meaningful to you,
c u
Eric
next prev parent reply other threads:[~2006-12-11 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 19:34 noexec=on doesn't work John Richard Moser
2006-12-09 20:03 ` Kyle McMartin
2006-12-09 20:10 ` John Richard Moser
2006-12-11 19:53 ` Eric Piel [this message]
2006-12-11 22:01 ` John Richard Moser
2006-12-14 21:22 ` Bill Davidsen
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=457DB755.1000100@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=kyle@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox