public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, sds@tycho.nsa.gov,
	selinux@tycho.nsa.gov, alan@redhat.com, chrisw@redhat.com,
	hpa@zytor.com, akpm@linux-foundation.org
Subject: Re: [PATCH 3/3-v2] security: allow capable check to permit mmap or low vm space
Date: Tue, 27 Nov 2007 11:38:24 +1100 (EST)	[thread overview]
Message-ID: <Xine.LNX.4.64.0711271137300.26171@us.intercode.com.au> (raw)
In-Reply-To: <1196120866.16779.16.camel@localhost.localdomain>

On Mon, 26 Nov 2007, Eric Paris wrote:

> On a kernel with CONFIG_SECURITY but without an LSM which implements
> security_file_mmap it is impossible for an application to mmap addresses
> lower than mmap_min_addr.  Based on a suggestion from a developer in the
> openwall community this patch adds a check for CAP_SYS_RAWIO.  It is
> assumed that any process with this capability can harm the system a lot
> more easily than writing some stuff on the zero page and then trying to
> get the kernel to trip over itself.  It also means that programs like X
> on i686 which use vm86 emulation can work even with mmap_min_addr set.
> 
> Signed-off-by: Eric Paris <eparis@redhat.com>

Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/selinux-2.6.git#for-akpm

If nobody hollers, I'll push it to Linus when the next merge window opens.


- James
-- 
James Morris
<jmorris@namei.org>

      reply	other threads:[~2007-11-27  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 23:47 [PATCH 3/3-v2] security: allow capable check to permit mmap or low vm space Eric Paris
2007-11-27  0:38 ` James Morris [this message]

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=Xine.LNX.4.64.0711271137300.26171@us.intercode.com.au \
    --to=jmorris@namei.org \
    --cc=akpm@linux-foundation.org \
    --cc=alan@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=eparis@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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