From: Ingo Molnar <mingo@elte.hu>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Hugh Dickins <hugh@veritas.com>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Document randomize_va_space and CONFIG_COMPAT_BRK (was Re: [PATCH 2/2] ASLR: add possibility for more fine-grained tweaking)
Date: Thu, 7 Feb 2008 00:10:40 +0100 [thread overview]
Message-ID: <20080206231040.GA6225@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0802061650230.30955@jikos.suse.cz>
* Jiri Kosina <jkosina@suse.cz> wrote:
> On Wed, 6 Feb 2008, Ingo Molnar wrote:
>
> > i've already added the patch below to x86.git.
>
> OK, cool, thanks.
>
> Still, I think that we want the Documentation/sysctl/kernel.txt part
> of my patch probably. Updated patch below.
thanks, applied.
i'm wondering about the following detail: i guess on 64-bit x86 kernels
we could default to !CONFIG_COMPAT_BRK? In 1997 there was no 64-bit x86.
Maybe for compat 32-bit binaries we could keep it off, but always do it
for 64-bit binaries.
Ingo
next prev parent reply other threads:[~2008-02-06 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 13:45 [PATCH 0/2] brk and randomization fixes Jiri Kosina
2008-02-06 13:45 ` [PATCH 1/2] brk: check the lower bound properly Jiri Kosina
2008-02-06 13:45 ` [PATCH 2/2] ASLR: add possibility for more fine-grained tweaking Jiri Kosina
2008-02-06 13:49 ` Ingo Molnar
2008-02-06 16:26 ` [PATCH] Document randomize_va_space and CONFIG_COMPAT_BRK (was Re: [PATCH 2/2] ASLR: add possibility for more fine-grained tweaking) Jiri Kosina
2008-02-06 23:10 ` Ingo Molnar [this message]
2008-02-07 9:49 ` Jiri Kosina
2008-02-07 14:30 ` Jiri Kosina
2008-02-07 15:01 ` Ingo Molnar
2008-02-07 10:23 ` [PATCH 2/2] ASLR: add possibility for more fine-grained tweaking Geert Uytterhoeven
2008-02-07 10:31 ` Ismail Dönmez
2008-02-07 10:32 ` Ingo Molnar
2008-02-07 10:43 ` Geert Uytterhoeven
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=20080206231040.GA6225@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hugh@veritas.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=randy.dunlap@oracle.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