public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bart Oldeman" <bartoldeman@users.sourceforge.net>
To: linux-msdos@vger.kernel.org, ivan <pivo@pobox.sk>
Subject: Re: LOWRAM mmap: Invalid argument
Date: Sat, 12 Apr 2008 13:51:54 -0400	[thread overview]
Message-ID: <c3d607cc0804121051u6cd29066t74ead153ac80e2a9@mail.gmail.com> (raw)
In-Reply-To: <20080412160908.GC16562@mola>

Hi,

you can check the value of
/proc/sys/vm/mmap_min_addr
and if it is non-zero, use
echo 0 > /proc/sys/vm/mmap_min_addr

I am not sure what Ubuntu has been up to exactly: this is something
that only works with SELinux enabled in enforcing mode.

This is the help:
+config SECURITY_DEFAULT_MMAP_MIN_ADDR
+        int "Low address space to protect from user allocation"
+        depends on SECURITY
+        default 0
+        help
+         This is the portion of low virtual memory which should be protected
+         from userspace allocation.  Keeping a user from writing to low pages
+         can help reduce the impact of kernel NULL pointer bugs.
+
+         For most users with lots of address space a value of 65536 is
+         reasonable and should cause no problems.  Programs which use vm86
+         functionality would either need additional permissions from either
+         the LSM or the capabilities module or have this protection disabled.
+
+         This value can be changed after boot using the
+         /proc/sys/vm/mmap_min_addr tunable.
+
+

I am not sure how to give DOSEMU special permission -- maybe you could
ask Ubuntu kernel maintainers about why they changed mmap_min_addr?

(o and this is speculation on my part, perhaps there is a different
problem in which case I don't know).

Bart

  reply	other threads:[~2008-04-12 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 16:09 LOWRAM mmap: Invalid argument ivan
2008-04-12 17:51 ` Bart Oldeman [this message]
2008-04-12 18:24   ` ivan
2010-09-20 19:19   ` marc.cunning

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=c3d607cc0804121051u6cd29066t74ead153ac80e2a9@mail.gmail.com \
    --to=bartoldeman@users.sourceforge.net \
    --cc=linux-msdos@vger.kernel.org \
    --cc=pivo@pobox.sk \
    /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