From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
Cc: Stuart_Hayes-DYMqY+WieiM@public.gmane.org,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Robert Moore
<robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: stack overflow
Date: 10 Mar 2004 13:44:46 -0500 [thread overview]
Message-ID: <1078944286.2557.55.camel@dhcppc4> (raw)
In-Reply-To: <20040310133208.GC12272-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
On Wed, 2004-03-10 at 08:32, Andi Kleen wrote:
> If you have some recursion either fix it or at least add an error
> out when the stack gets too low. We can add an "stack_left" function
> exported by the architecture.
I think we'll want to put some fun-time sanity checks for illegal
recursion into the interpreter. That should be less invasive than doing
the full blown stack check -- which can be enabled as a separate DEBUG
test when needed.
> > Sorting the list of stack frame sizes below shows
> > acpi_evaluate_integer() is the winner with 320 bytes on the stack. Note
> > that this isn't from passing structures, but from allocating local
> > structures. On i386 acpi_parse_object is 124 bytes, on x86_64 it will
> > be bigger...
>
> I would suggest to fix anything > 100 bytes at least
> (and double check anything that could be expanded on 64bit)
Agreed, Bob and I will fix the big stack users.
thanks,
-Len
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-10 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 16:43 stack overflow Stuart_Hayes-DYMqY+WieiM
[not found] ` <CE41BFEF2481C246A8DE0D2B4DBACF4F128AA4-novRXWwkcpil7xnNSM18fRtLTTO9Z+wMojBamW5iJbs@public.gmane.org>
2004-03-08 18:26 ` Andi Kleen
[not found] ` <20040308182630.GB9490-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-03-09 7:17 ` Len Brown
2004-03-10 4:33 ` Len Brown
[not found] ` <1078893223.2346.585.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-10 13:32 ` Andi Kleen
[not found] ` <20040310133208.GC12272-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-03-10 18:44 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-09 18:34 Moore, Robert
2004-03-09 20:00 Stuart_Hayes-DYMqY+WieiM
2004-03-09 21:04 Stuart_Hayes-DYMqY+WieiM
2004-03-09 22:48 Moore, Robert
2004-03-10 15:56 Stuart_Hayes-DYMqY+WieiM
2004-03-10 17:08 Stuart_Hayes-DYMqY+WieiM
[not found] ` <CE41BFEF2481C246A8DE0D2B4DBACF4F020E5FD9-novRXWwkcpil7xnNSM18fRtLTTO9Z+wMojBamW5iJbs@public.gmane.org>
2004-03-10 18:40 ` Len Brown
2004-03-22 17:40 Stuart_Hayes-DYMqY+WieiM
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=1078944286.2557.55.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=Stuart_Hayes-DYMqY+WieiM@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ak-l3A5Bk7waGM@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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