From: David Howells <dhowells@redhat.com>
To: graff.yang@gmail.com
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org,
uclinux-dist-devel@blackfin.uclinux.org, graf.yang@analog.com
Subject: Re: [PATCH] mm/nommu.c: fix mmap failed due to the vm_region codes
Date: Thu, 24 Sep 2009 13:29:46 +0100 [thread overview]
Message-ID: <14655.1253795386@redhat.com> (raw)
In-Reply-To: <1253792279-30623-1-git-send-email-graff.yang@gmail.com>
<graff.yang@gmail.com> wrote:
> Due to the new vm_region codes, mmap will failed if it is MAP_PRIVATE,
> or the get_unmapped_area() not do actual things.
Hmmm... Seems one of my debugging patches had a work around for this - all it
did was #ifdef-out the first if-statement in do_mmap_private(). That, however,
prevents XIP.
Sadly, your patch doesn't completely fix the problem either. The BUG in
add_nommu_region() barks.
Let me poke at it some more.
David
prev parent reply other threads:[~2009-09-24 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 11:37 [PATCH] mm/nommu.c: fix mmap failed due to the vm_region codes graff.yang
2009-09-24 12:29 ` David Howells [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=14655.1253795386@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=graf.yang@analog.com \
--cc=graff.yang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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