Re: [2.6 patch] i386: always use 4k stacks

From: Jörn Engel (joern_at_wohnheim.fh-wedel.de)
Date: 11/16/05

  • Next message: Serge E. Hallyn: "Re: [RFC] [PATCH 12/13] Change pid accesses: ia64 and mips"
    Date:	Wed, 16 Nov 2005 14:51:16 +0100
    To: Andi Kleen <ak@suse.de>
    
    

    On Wed, 16 November 2005 13:57:36 +0100, Andi Kleen wrote:
    >
    > I think it's in general risky. It's like balancing without a safety
    > net. Might be a nice hobby, but for real production you want a safety
    > net. That's simple because there are likely some code paths through
    > the code that need more stack space and that are rarely hit (and
    > cannot be easily found by static analysis, e.g. if they involve
    > indirect pointers or particularly complex configuration setups).

    It isn't that hard to find such places. Trouble is that you find so
    many of them and it takes quite a while to go through them all. Years
    is a good unit for "quite a while".

    Jörn

    -- 
    With a PC, I always felt limited by the software available. On Unix, 
    I am limited only by my knowledge.
    -- Peter J. Schoenster
    -
    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/
    

  • Next message: Serge E. Hallyn: "Re: [RFC] [PATCH 12/13] Change pid accesses: ia64 and mips"

    Relevant Pages

    • Re: [2.6 patch] i386: always use 4k stacks
      ... but for real production you want a safety ... That's simple because there are likely some code paths through ... Map a blank ro page beneath the address range when stack memory is ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 4g/4g for 2.6.6
      ... > safety we assume 32G is the very safe limit). ... Just how many 3GB sized processes can you run on that ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH 2/5] selinux: adds a private inode operation
      ... Shouldn't this be using dget_parentfor safety? ... Don't we also need to modify inode_has_permto skip checking if the ... directories with the kernel SID upon such lookups. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 4g/4g for 2.6.6
      ... safety we assume 32G is the very safe limit). ... send the line "unsubscribe linux-kernel" in ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)