All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: " Oliver Pinter (Pintér Olivér) " <oliver.pntr@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.23(?)=<] X used greatest stack depth: N bytes left
Date: Fri, 28 Dec 2007 15:32:58 -0800	[thread overview]
Message-ID: <20071228153258.bef76bb2.randy.dunlap@oracle.com> (raw)
In-Reply-To: <6101e8c40712281311p446f64e1xb28f8fc273545041@mail.gmail.com>

On Fri, 28 Dec 2007 22:11:25 +0100 Oliver Pinter (Pintér Olivér) wrote:

> in newer kernel I recently see this warnings:
> 
> X used greatest stack depth: N bytes left
> 
> X E { program name }
> N E { x byte }
> 
> ----------------8<--------------
> ...
> khelper used greatest stack depth: 7496 bytes left
> khelper used greatest stack depth: 7184 bytes left
> ...
> khelper used greatest stack depth: 6328 bytes left
> stty used greatest stack depth: 6180 bytes left
> mount used greatest stack depth: 6156 bytes left
> mknod used greatest stack depth: 5932 bytes left
> ...
> wpa_supplicant used greatest stack depth: 5740 bytes left
> ...
> dhclient3 used greatest stack depth: 5500 bytes left
> ----------------8<--------------
> 
> it is the "results" of the CONFIG_DEBUG_STACKOVERFLOW=y
> CONFIG_DEBUG_STACK_USAGE=y options or it's other problem or feature?

CONFIG_DEBUG_STACK_USAGE, in kernel/exit.c:

---
~Randy
desserts:  http://www.xenotime.net/linux/recipes/

  reply	other threads:[~2007-12-28 23:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 21:11 [2.6.23(?)=<] X used greatest stack depth: N bytes left Oliver Pinter (Pintér Olivér)
2007-12-28 23:32 ` Randy Dunlap [this message]
2007-12-29  0:58   ` Oliver Pinter (Pintér Olivér)
2007-12-29  1:13     ` Randy Dunlap
2007-12-29  2:35       ` Oliver Pinter (Pintér Olivér)
2007-12-29  2:15     ` Valdis.Kletnieks

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=20071228153258.bef76bb2.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.pntr@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.