public inbox for kernel-hardening@lists.openwall.com
 help / color / mirror / Atom feed
From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] [RFC] x86, mm: start mmap allocation for libs from low addresses
Date: Tue, 6 Sep 2011 09:05:54 +0400	[thread overview]
Message-ID: <20110906050554.GA3889@openwall.com> (raw)
In-Reply-To: <20110905124647.GA10247@albatros>

On Mon, Sep 05, 2011 at 04:46:47PM +0400, Vasiliy Kulikov wrote:
> Hmm, yes, looks like I've lost the thread some time ago :(  A good
> description definitely needs much longer and scrupulous analysis.

Or alternatively it may choose not to go into detail at all, which is a
safer bet. ;-)

> Probably there is a public paper with a review/analysis/benefits of
> ASCII-armor that we're able to refer in the patch description?  I cannot
> find any rigorous paper, unfortunately.

I'm not aware of such paper.

> On Sun, Sep 04, 2011 at 03:57 +0400, Solar Designer wrote:
> > solar@host:~/kernel/mainline/linux-3.0.4 $ fgrep -rl CONFIG_VM86 .
> > ./arch/x86/kernel/Makefile
> > ./arch/x86/kernel/entry_32.S
> > ./arch/x86/include/asm/vm86.h
> > ./arch/x86/include/asm/processor-flags.h
> > 
> > Looks like there's no Kconfig option for this - perhaps add it with a
> > separate patch?
> 
> Since 2.6.x CONFIG_ prefix is not used in Kconfig files:
> 
> $ grep -w VM86 arch/x86/Kconfig
> config VM86
>     bool "Enable VM86 support" if EXPERT

Oh, of course.  Sometimes I say/do dumb things.

Turns out this stuff is also present in RHEL5/OpenVZ kernels, so we
might want to turn on CONFIG_EMBEDDED and disable CONFIG_VM86 in Owl
kernel builds, even before we move to newer kernels.

Alexander

  reply	other threads:[~2011-09-06  5:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 10:29 [kernel-hardening] [RFC] x86, mm: start mmap allocation for libs from low addresses Vasiliy Kulikov
2011-08-12 10:58 ` Solar Designer
2011-08-12 11:05   ` Vasiliy Kulikov
2011-08-25 17:19   ` Vasiliy Kulikov
2011-08-25 17:39     ` Solar Designer
2011-09-02 18:29     ` Solar Designer
2011-09-03 11:18       ` Vasiliy Kulikov
2011-09-03 23:57         ` Solar Designer
2011-09-05 12:46           ` Vasiliy Kulikov
2011-09-06  5:05             ` Solar Designer [this message]
2011-09-07  9:09               ` Vasiliy Kulikov
2011-09-07  9:30                 ` Solar Designer
2011-09-07  9:34                   ` Vasiliy Kulikov
2011-09-07  9:43                     ` Solar Designer
2011-09-07  9:55                       ` Vasiliy Kulikov
2011-09-07 10:16                         ` Solar Designer
2011-09-07 11:01                           ` Vasiliy Kulikov
2011-09-02 23:34     ` Solar Designer
2011-09-03 12:12       ` Vasiliy Kulikov
2011-09-03 23:40         ` Solar Designer
2011-09-04  7:21         ` Vasiliy Kulikov
2011-08-12 23:19 ` [kernel-hardening] " H. Peter Anvin
2011-08-13  6:26   ` Vasiliy Kulikov
2011-08-16  9:05   ` Vasiliy Kulikov
2011-08-22 10:17     ` Vasiliy Kulikov
2011-08-22 17:24       ` H. Peter Anvin
2011-08-22 20:14         ` Vasiliy Kulikov
2011-08-22 20:17           ` H. Peter Anvin
2011-08-23  6:41             ` Vasiliy Kulikov

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=20110906050554.GA3889@openwall.com \
    --to=solar@openwall.com \
    --cc=kernel-hardening@lists.openwall.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