mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ravi Wijayaratne <ravi_wija@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Stack overflow ?
Date: Mon, 6 May 2002 09:53:36 -0700 (PDT)	[thread overview]
Message-ID: <20020506165336.93440.qmail@web13105.mail.yahoo.com> (raw)

Hi All,

I applied Tigran's 8k->16k large stack patch to
2.4.18. When I look at /proc/stack I see that a
process insmod is using 0x2000=8k stack. My
undertstanding is that the stack size increase should
not have affected the amount of stack used by any
process. 

If that is the case how did my system survive without
the patch when the whole task_struct is wiped out by a
process using a stack size of 8k. I have been running
heavy I/O on this system (A file server) for a couple
of days without the patch. Nothing adverese happened.

Can this happen or are the contents put to /proc/stack
in the patch is wrong. I looked at the patch carefully
and all seems to be ok to me. Has any one had a
similar experience before ?

To further analyze the problem I called BUG() when the
stack size ever increased more than 8k in schedule()
After running ksymoops I see that this is happening
when I try to access routines in i2c.o which seem to
have a deep call stack.

Thank you
Ravi

=====
------------------------------
Ravi Wijayaratne

__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

             reply	other threads:[~2002-05-06 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06 16:53 Ravi Wijayaratne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-26 10:03 stack overflow? Christian Widmer
2001-09-26 13:29 ` Brian Gerst
2001-09-26 13:46   ` Christian Widmer

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=20020506165336.93440.qmail@web13105.mail.yahoo.com \
    --to=ravi_wija@yahoo.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®