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
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.
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:27 EST