From: "Albert Cahalan" <acahalan@gmail.com>
To: "Michel Dänzer" <michel@tungstengraphics.com>
Cc: linuxppc-dev@ozlabs.org,
debian-powerpc <debian-powerpc@lists.debian.org>
Subject: Re: [PATCH] no-execute -- please test
Date: Mon, 14 Aug 2006 12:02:06 -0400 [thread overview]
Message-ID: <787b0d920608140902m3da2592ejbd5a1a9cee3182e4@mail.gmail.com> (raw)
In-Reply-To: <1155547172.12664.115.camel@thor.lorrainebruecke.local>
On 8/14/06, Michel D=E4nzer <michel@tungstengraphics.com> wrote:
> On Sun, 2006-08-13 at 23:20 -0400, Albert Cahalan wrote:
> >
> > If you want heap protection, change VM_DATA_DEFAULT_FLAGS32
> > in include/asm-powerpc/page.h to be like VM_STACK_DEFAULT_FLAGS.
> > I'd love to hear if anybody can get X to start with this change.
> > For me (Xorg w/ ATI) a module load fails.
>
> Which versions of the X server and driver, and which module fails to
> load exactly how? As of X.Org 6.9, the X server no longer uses a custom
> module loader but just dlopen and friends.
xorg 1:7.0.20
xserver-xorg 1:7.0.20
xserver-xorg-core 1:1.0.2-8
xserver-xorg-video-ati 1:6.5.8.0-1
Debian's aptitude program didn't complain, and I didn't do anything
like holding back a package, so the version mismatch isn't my doing.
What calls does the old X server use to allocate the memory?
Knowing the mmap() and/or mprotect() args might help to let
the old server still work.
If dlopen() doesn't need to patch up the code, W^X could be
enforced on the new X server.
next prev parent reply other threads:[~2006-08-14 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 3:20 [PATCH] no-execute -- please test Albert Cahalan
2006-08-14 4:00 ` Paul Mackerras
2006-08-14 4:41 ` Albert Cahalan
2006-08-14 23:34 ` Paul Mackerras
2006-08-16 23:55 ` Benjamin Herrenschmidt
2006-08-20 17:48 ` Albert Cahalan
2006-08-14 4:02 ` Paul Mackerras
2006-08-14 4:33 ` Albert Cahalan
2006-08-14 8:46 ` Andreas Schwab
2006-08-14 9:19 ` Michel Dänzer
2006-08-14 16:02 ` Albert Cahalan [this message]
2006-08-14 16:08 ` Albert Cahalan
2006-08-14 16:20 ` Michel Dänzer
2006-08-19 3:47 ` Albert Cahalan
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=787b0d920608140902m3da2592ejbd5a1a9cee3182e4@mail.gmail.com \
--to=acahalan@gmail.com \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michel@tungstengraphics.com \
/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;
as well as URLs for NNTP newsgroup(s).