All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.16.16 Parameter-controlled mmap/stack randomization
Date: Sat, 20 May 2006 01:23:54 -0400	[thread overview]
Message-ID: <446EA7EA.2070804@comcast.net> (raw)
In-Reply-To: <446E6A3B.8060100@comcast.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



John Richard Moser wrote:
[...]

> 
> There's a few other things I want to get done, but I'll worry about
> those later.  They are:
> 
>  - Take care of the FIXME in that __init code in fs/exec.c to use
> architecture-specific #defines for the maximum values of these
> parameters, probably in asm-* somewhere.
[...]

Working on this right now.  I've fixed the 4096 hard-coded page sizes
and made them work with PAGE_SIZE; the stack was fun, I had to use a
long_log2() and calculate how many page_random_bits were possible and
cut that out to see if any vma_random_bits were left and how many.  :)

I'm also looking at using STACK_RANDOM_BITS_MAX_X86 or something because
of IA-32 emulation on x86-64.  I definitely need to figure out how to
make that work cleanly; on x86-64 we may have more stack/heap entropy
than sane, and I'd rather limit that (at first; later comes--
confusion-- stack_random_bits32= mmap_random_bits32=).

While I'm at it, does anyone see anything else glaring I should fix?  (I
am actually trying to get this merged, yes...)
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

    Creative brains are a valuable, limited resource. They shouldn't be
    wasted on re-inventing the wheel when there are so many fascinating
    new problems waiting out there.
                                                 -- Eric Steven Raymond

    We will enslave their women, eat their children and rape their
    cattle!
                  -- Bosc, Evil alien overlord from the fifth dimension
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBRG6n4As1xW0HCTEFAQJryRAAgGr+XuOwG2hIVx+1RNmqcyVUC0sYew3D
9OFkV4PcyIUwGBmJcUWXzkV46av3Fz3Gk5Dm7X7KMpbroUz0big4MiZTeLRPsoCN
s99pDqciPe+YGjqj3KcIdwFT+ryUSpIAI4K8pMu2unqejf53T0QQR/7w7bkUqoOe
tj/L5GwubpJH2SNvWuBwHHNtOisuSBkXYIj90swfijbmiccAWki7i50I7Svd14db
uYWS8RvxMTUYEKbhW363OdlkVp0cvrbaIh2UYcEH4P2g7tcdzgG/aP9dUzQPDk0W
r5ltVMlGbVp1K1IPXuEn8S8gSmufPCq8AahQlVhiMiIqk4K1cw87tzY6H4UjE0dH
AyQ+NLQKy8RsOYDnfb4eM/x3JDJjF8RHHxPqVuRTRtA+tA+N2GKFwbOMsVvGj+PV
GYzaH/XAKzvccWWBlhFu2YQG9ZQqy+dpfCotvrbYQPfiuYj7+1yRdE7BaFUAMO6P
MVXf+tY1wzIZ9vEjIhYZtbq4VHNzwp43Jm0sHLdkUm9BPJzLoZbExC86BY5L6U2X
QG0SV3EyzT7wUga+28jbcG77aFEVR6ZhNLa3MFVqO6hF7ApTiJRooU5k4m7XUzx7
qlhhFFcB4HFTFV6o9Usp7YkGQnwmVKmtFOz/nY0COuJiQCRU4jby30NgPhCH+li2
VJz/1v+bBCs=
=yTDy
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2006-05-20  5:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-20  1:00 [PATCH] 2.6.16.16 Parameter-controlled mmap/stack randomization John Richard Moser
2006-05-20  3:36 ` John Richard Moser
2006-05-20  5:23 ` John Richard Moser [this message]
2006-05-20 13:47 ` Arjan van de Ven
2006-05-20 15:23   ` John Richard Moser
2006-05-22  1:06     ` Pavel Machek
2006-05-22  2:46       ` John Richard Moser
2006-05-22  8:33         ` Pavel Machek
2006-05-22 16:31           ` John Richard Moser
2006-05-22 17:00             ` Pavel Machek
2006-05-22 17:54               ` John Richard Moser
2006-05-22 18:40                 ` Pavel Machek
2006-05-22 19:02                   ` John Richard Moser
2006-05-22 19:12                     ` Pavel Machek
2006-05-22 19:27                       ` John Richard Moser
2006-05-22 19:41                         ` Pavel Machek
2006-05-22 20:05                           ` John Richard Moser
2006-05-23  1:05             ` Arjan van de Ven
2006-05-23  1:34               ` John Richard Moser
2006-05-20 17:13 ` John Richard Moser

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=446EA7EA.2070804@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    /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.