From: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
To: "'Anton Blanchard'" <anton@samba.org>,
"'Peter Bergner'" <bergner@vnet.ibm.com>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: TASK_UNMAPPED_BASE
Date: Fri, 6 Feb 2004 11:53:32 +0100 [thread overview]
Message-ID: <000901c3ec9f$76acd7e0$0a01a8c0@LUMENTIS02> (raw)
In-Reply-To: <20040205170657.GA19011@krispykreme>
> > The problem with a TASK_UNMAPPED_BASE that was "too low"
> > was referring to the bug where we always loaded ld.so at
> > TASK_UNMAPPED_BASE even though that adress was in the middle of the
> > bss. Now that has been fixed, "too low" isn't a concern anymore.
> >
> > However, I'm not sure moving the TASK_UNMAPPED_BASE below the text
> > section will work. It's used for more than just loading shared libs.
> > Anonymous mmap areas and the heap are all located relative to it.
>
> That reminded me of a patch wli did to rearrange how things are
> allocated. I wonder if doing something radical like this will work on
> ppc32.
[SNIP patch]
Hi Anton
I tried your patch on my 2.4 kernel.
uClibc boots fine with the libs loaded towards lower addresses.
glibc won't boot, hangs direcly after mount.
Jocke
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-06 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 13:05 TASK_UNMAPPED_BASE Joakim Tjernlund
2004-02-03 15:22 ` TASK_UNMAPPED_BASE Franz Sirl
2004-02-03 16:51 ` TASK_UNMAPPED_BASE Joakim Tjernlund
2004-02-04 14:37 ` TASK_UNMAPPED_BASE Peter Bergner
2004-02-04 14:47 ` TASK_UNMAPPED_BASE Anton Blanchard
2004-02-04 21:58 ` TASK_UNMAPPED_BASE Peter Bergner
2004-02-05 8:57 ` TASK_UNMAPPED_BASE Joakim Tjernlund
2004-02-05 16:34 ` TASK_UNMAPPED_BASE Peter Bergner
2004-02-05 17:06 ` TASK_UNMAPPED_BASE Anton Blanchard
2004-02-06 10:53 ` Joakim Tjernlund [this message]
2004-02-05 17:10 ` TASK_UNMAPPED_BASE Joakim Tjernlund
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='000901c3ec9f$76acd7e0$0a01a8c0@LUMENTIS02' \
--to=joakim.tjernlund@lumentis.se \
--cc=anton@samba.org \
--cc=bergner@vnet.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).