From: Marc-Christian Petersen <m.c.p@kernel.linux-systeme.com>
To: lorenzo@gnu.org, pageexec@freemail.hu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel hacking option "Debug memory allocations" possible leak of PaX memory randomization
Date: Tue, 13 Jul 2004 16:01:39 +0200 [thread overview]
Message-ID: <200407131601.39909@WOLK> (raw)
In-Reply-To: <1089726693.3283.21.camel@localhost>
On Tuesday 13 July 2004 15:51, Lorenzo Hernandez Garcia-Hierro wrote:
Hi Lorenzo,
> Is anyone of you having the same situation, is it an unexpected behavior or
> it's a bug on the kernel source?
> Is that option non-compatible with PaX RANDSTACK and the rest of PaX's
> memory randomization features?
CC pageexec at freemail dot hu - He's the PaX programmer.
ciao, Marc
next prev parent reply other threads:[~2004-07-13 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 13:51 Kernel hacking option "Debug memory allocations" possible leak of PaX memory randomization Lorenzo Hernandez Garcia-Hierro
2004-07-13 14:01 ` Marc-Christian Petersen [this message]
2004-07-13 14:10 ` Lorenzo Hernandez Garcia-Hierro
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=200407131601.39909@WOLK \
--to=m.c.p@kernel.linux-systeme.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@gnu.org \
--cc=pageexec@freemail.hu \
/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