Re: vma->vm_end > 0x60000000

Andreas Schwab (schwab@suse.de)
07 Dec 2001 09:33:12 +0100


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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/