public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] UDEREF vs. Apache MMAP
Date: Sat, 08 Jan 2011 08:12:48 -0500	[thread overview]
Message-ID: <4D2862D0.9050407@gentoo.org> (raw)
In-Reply-To: <4D27EEA5.6080301@orlitzky.com>

On 01/07/2011 11:57 PM, Michael Orlitzky wrote:
> I was able to figure out my new apache problem. It seems that
> PAX_MEMORY_UDEREF and apache's EnableMMAP directive don't get along
> sometimes:
> 
>   http://httpd.apache.org/docs/2.2/mod/core.html#enablemmap
> 
> With UDEREF enabled and MMAP on, I get random inappropriate 206 response
> codes everywhere causing headers, images, and CSS files to fail to
> transfer properly.
> 
> This is sufficiently into the realm of what I consider voodoo. Is there
> anything I can do to help narrow down the problem, or should I just
> disable MMAP and be happy?

It sounds like a problem in the way apache is doing the mmap and PaX is
killing it.  The new stricter PaX rules don't allow the permission of
allocated pages to be changed, eg RW -> RX, or to be RWX.  This has come
up elsewhere, see

   http://bugs.gentoo.org/show_bug.cgi?id=329499

To verify my suspicion, an strace would be helpful.  If you don't mind,
open up a bug with your findings, give your emerge --info, the flags you
used with apache, and an strace of apache going bad.  This will be a
start for us.

-- 
Anthony G. Basile, Ph.D.
Gentoo Developer



      parent reply	other threads:[~2011-01-08 14:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08  4:57 [gentoo-hardened] UDEREF vs. Apache MMAP Michael Orlitzky
2011-01-08 12:09 ` pageexec
2011-01-08 18:22   ` Anthony G. Basile
2011-01-08 20:21     ` Michael Orlitzky
2011-01-10 11:16     ` pageexec
2011-01-08 13:12 ` Anthony G. Basile [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=4D2862D0.9050407@gentoo.org \
    --to=blueness@gentoo.org \
    --cc=gentoo-hardened@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox