From: Andreas Schwab <schwab@suse.de>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: vma->vm_end > 0x60000000
Date: 07 Dec 2001 09:33:12 +0100 [thread overview]
Message-ID: <jevgfj8m5z.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10010311645420.400-100000@cassiopeia.home> <20011206191734.B818@holomorphy.com>
In-Reply-To: <20011206191734.B818@holomorphy.com> (William Lee Irwin III's message of "Thu, 6 Dec 2001 19:17:34 -0800")
William Lee Irwin III <wli@holomorphy.com> writes:
|> On Tue, Oct 31, 2000 at 04:48:11PM +0100, Geert Uytterhoeven wrote:
|> > In fs/proc/array.c:proc_pid_statm() there is this test block:
|> >
|> > if (vma->vm_flags & VM_EXECUTABLE)
|> > trs += pages; /* text */
|> > else if (vma->vm_flags & VM_GROWSDOWN)
|> > drs += pages; /* stack */
|> > else if (vma->vm_end > 0x60000000)
|> > lrs += pages; /* library */
|> > else
|> > drs += pages;
|> >
|> > Is there any special reason for the hardcoded constant `0x60000000'?
|> > In the Linux/m68k tree, we use TASK_UNMAPPED_BASE instead. But I don't know
|> > why.
|>
|> I think this is an old x86 load address for an ELF interpreter.
No, it is a leftover from the a.out times. IMHO it should be removed
completely. "Library pages" has no meaning for ELF.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-12-07 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-31 15:48 vma->vm_end > 0x60000000 Geert Uytterhoeven
2001-12-07 3:17 ` William Lee Irwin III
2001-12-07 8:33 ` Andreas Schwab [this message]
2001-12-07 8:47 ` William Lee Irwin III
2001-12-07 20:16 ` Albert D. Cahalan
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=jevgfj8m5z.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=wli@holomorphy.com \
/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