lkml.org 
[lkml]   [2003]   [Apr]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: TASK_UNMAPPED_BASE & stack location
    Date
    Followup to:  <459930000.1051302738@[10.10.2.4]>
    By author: "Martin J. Bligh" <mbligh@aracnet.com>
    In newsgroup: linux.dev.kernel
    >
    > Is there any good reason we can't remove TASK_UNMAPPED_BASE, and just shove
    > libraries directly above the program text? Red Hat seems to have patches to
    > dynamically tune it on a per-processes basis anyway ...
    >
    > Moreover, can we put the stack back where it's meant to be, below the
    > program text, in that wasted 128MB of virtual space? Who really wants
    > > 128MB of stack anyway (and can't fix their app)?
    >

    That space is NULL pointer trap zone. NULL pointer trapping -> good.

    -hpa
    --
    <hpa@transmeta.com> at work, <hpa@zytor.com> in private!
    "Unix gives you enough rope to shoot yourself in the foot."
    Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 13:35    [W:0.035 / U:30.288 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site