public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: vma->vm_end > 0x60000000
Date: Thu, 6 Dec 2001 19:17:34 -0800	[thread overview]
Message-ID: <20011206191734.B818@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10010311645420.400-100000@cassiopeia.home>
In-Reply-To: <Pine.LNX.4.10.10010311645420.400-100000@cassiopeia.home>; from geert@linux-m68k.org on Tue, Oct 31, 2000 at 04:48:11PM +0100

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. Would
you be happy with ELF_ET_DYN_BASE? I made a fairly small patch that
deals with that.


Cheers,
Bill

  reply	other threads:[~2001-12-07  3:18 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 [this message]
2001-12-07  8:33   ` Andreas Schwab
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=20011206191734.B818@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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