mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Oliver Pinter (Pintér Olivér)" <oliver.pntr@gmail.com>
To: "Randy Dunlap" <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org,
	"Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Subject: Re: [2.6.23(?)=<] X used greatest stack depth: N bytes left
Date: Sat, 29 Dec 2007 03:35:56 +0100	[thread overview]
Message-ID: <6101e8c40712281835m6205fe91p8ecf37a2eac9d432@mail.gmail.com> (raw)
In-Reply-To: <20071228171312.baa0776b.randy.dunlap@oracle.com>

On 12/29/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Sat, 29 Dec 2007 01:58:44 +0100 Oliver Pinter (Pintér Olivér) wrote:
>
> > On 12/29/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > > 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:
> > >
> > > ---
> >
> > sure, but to 2.6.22 or 2.6.23-rcX (with merged the cfs scheduler)
> > don't show this warnings, but the CONFIG_DEBUG_STACK_USAGE is enabled.
>
> Sorry, I couldn't tell that you were asking more than that.
>
> In 2.6.22, CONFIG_DEBUG_STACK_USAGE only causes output during
> sysrq-W (show blocked state).
>
> In 2.6.24-rc, CONFIG_DEBUG_STACK_USAGE also causes output during
> process exit, which is what you are seeing.
>
> Does that help?

yes, thanks, then it's the answer

sorry, for my bad  composition/spelling

-- 
Thanks,
Oliver

  reply	other threads:[~2007-12-29  2:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 21:11 Oliver Pinter (Pintér Olivér)
2007-12-28 23:32 ` Randy Dunlap
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) [this message]
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=6101e8c40712281835m6205fe91p8ecf37a2eac9d432@mail.gmail.com \
    --to=oliver.pntr@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®