From: Arjan van de Ven <arjanv@redhat.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: arch_get_unmapped_area_topdown vs stack reservations
Date: Wed, 18 Aug 2004 08:11:21 +0200 [thread overview]
Message-ID: <20040818061121.GB21740@devserv.devel.redhat.com> (raw)
In-Reply-To: <170170000.1092781114@flay>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
On Tue, Aug 17, 2004 at 03:18:34PM -0700, Martin J. Bligh wrote:
> I worry that the current code will allow us to intrude into the
> reserved stack space with a vma allocation if it's requested at
> an address too high up. One could argue that they got what they
> asked for ... but not sure we should be letting them do that?
well even the non-flexmmap code allows this.... what is the problem ?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-18 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 22:18 arch_get_unmapped_area_topdown vs stack reservations Martin J. Bligh
2004-08-18 6:11 ` Arjan van de Ven [this message]
2004-08-18 6:18 ` Martin J. Bligh
2004-08-18 6:36 ` Arjan van de Ven
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=20040818061121.GB21740@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.