From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andi Kleen <ak@suse.de>, Jamie Lokier <jamie@shareable.org>
Cc: torvalds@osdl.org, mingo@elte.hu, benh@kernel.crashing.org,
linux-kernel@vger.kernel.org, akpm@osdl.org, drepper@redhat.com
Subject: Re: [BUG] get_unmapped_area() change -> non booting machine
Date: Fri, 13 Feb 2004 10:33:55 -0800 [thread overview]
Message-ID: <38670000.1076697235@flay> (raw)
In-Reply-To: <20040215062544.5e554a61.ak@suse.de>
--On Sunday, February 15, 2004 06:25:44 +0100 Andi Kleen <ak@suse.de> wrote:
> On Fri, 13 Feb 2004 03:26:04 +0000
> Jamie Lokier <jamie@shareable.org> wrote:
>
>> Linus Torvalds wrote:
>> > One option is to mark the brk() VMA's as being grow-up (which they are),
>> > and make get_unmapped_area() realize that it should avoid trying to
>> > allocate just above grow-up segments or just below grow-down segments.
>> > That's still something of a special case, but at least it's not "magic"
>> > any more, now it's more of a "makes sense".
>>
>> That reminds me. What happens when grow-down stack VMAs finally bump
>> into another VMA. Is there an unmapped guard page retained to segfault
>> the program, or does the program silently start overwriting the VMA it
>> bumped into?
>
> In the standard kernel it silently overwrites, but in 2.4-aa there was a patch forever
> that adds a guard page.
Do you happen to remember the name of the patch? Hunting in Andrea's tree
isn't always easy ;-)
M.
next prev parent reply other threads:[~2004-02-13 18:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 3:47 [BUG] get_unmapped_area() change -> non booting machine Benjamin Herrenschmidt
2004-02-10 16:25 ` Linus Torvalds
2004-02-10 17:37 ` Jamie Lokier
2004-02-10 22:25 ` Benjamin Herrenschmidt
2004-02-12 23:23 ` Andi Kleen
2004-02-12 10:04 ` Ingo Molnar
2004-02-12 16:36 ` Linus Torvalds
2004-02-12 17:02 ` Dave McCracken
2004-02-12 17:17 ` Linus Torvalds
2004-02-12 17:31 ` Dave McCracken
2004-02-12 18:19 ` Linus Torvalds
2004-02-12 18:25 ` Dave McCracken
2004-02-12 20:49 ` Benjamin Herrenschmidt
2004-02-13 3:26 ` Jamie Lokier
2004-02-15 5:25 ` Andi Kleen
2004-02-13 18:33 ` Martin J. Bligh [this message]
2004-02-13 1:52 ` Andi Kleen
2004-02-13 6:26 ` H. Peter Anvin
2004-02-10 22:17 ` Benjamin Herrenschmidt
2004-02-14 8:34 ` Andi Kleen
2004-02-11 23:23 ` Andi Kleen
2004-02-10 7:48 ` Benjamin Herrenschmidt
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=38670000.1076697235@flay \
--to=mbligh@aracnet.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=drepper@redhat.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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