public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: torvalds@osdl.org, benh@kernel.crashing.org,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [BUG] get_unmapped_area() change -> non booting machine
Date: Fri, 13 Feb 2004 00:23:58 +0100	[thread overview]
Message-ID: <20040213002358.1dd5c93a.ak@suse.de> (raw)
In-Reply-To: <20040210173738.GA9894@mail.shareable.org>

On Tue, 10 Feb 2004 17:37:38 +0000
Jamie Lokier <jamie@shareable.org> wrote:

 
> The real question is - why does malloc() break?  I'd expect malloc()
> to use MAP_ANON these days, when brk() fails.  But it seems not.

Yep, that's the real bug.

-Andi

  parent reply	other threads:[~2004-02-10 19:17 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 [this message]
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
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=20040213002358.1dd5c93a.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --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