From: Arjan van de Ven <arjanv@redhat.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
linux-kernel@vger.kernel.org,
Rik van Riel <riel@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [patch] larger kernel stack (8k->16k) per task
Date: Fri, 8 Feb 2002 11:57:55 -0500 [thread overview]
Message-ID: <20020208115755.E1429@devserv.devel.redhat.com> (raw)
In-Reply-To: <20020208110930.C1429@devserv.devel.redhat.com> <Pine.LNX.4.33.0202081645170.1359-100000@einstein.homenet>
In-Reply-To: <Pine.LNX.4.33.0202081645170.1359-100000@einstein.homenet>; from tigran@veritas.com on Fri, Feb 08, 2002 at 04:59:47PM +0000
On Fri, Feb 08, 2002 at 04:59:47PM +0000, Tigran Aivazian wrote:
> On Fri, 8 Feb 2002, Arjan van de Ven wrote:
> > If you need even more in your code (I assume you do otherwise you wouldn't
> > have done the work) then I really suggest you take a long hard look and fix
> > the obvious bugs or the design....
>
> Arjan, I completely agree with you, but please do not overlook one obvious
> thing -- sometimes (well, most of the time) in order to fix those stack
> corruption issues you _first_ need to apply this patch and then it becomes
> obvious that the reason for this "random" corruption is the stack
> overflow. A kernel panic is not shouting like "I am a stack overflow!"
Stack redzoning makes a lot of sense. And checking isn't that expensive...
next prev parent reply other threads:[~2002-02-08 16:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 16:06 [patch] larger kernel stack (8k->16k) per task Tigran Aivazian
2002-02-08 16:09 ` Arjan van de Ven
2002-02-08 16:59 ` Tigran Aivazian
2002-02-08 16:57 ` Arjan van de Ven [this message]
2002-02-08 17:23 ` Arjan van de Ven
2002-02-08 18:16 ` Alan Cox
2002-02-08 18:29 ` Richard B. Johnson
2002-02-08 18:38 ` Arjan van de Ven
2002-02-08 20:54 ` Ingo Molnar
2002-02-08 18:15 ` Alan Cox
2002-02-08 20:22 ` Jes Sorensen
2002-02-08 21:12 ` Mike Fedyk
2002-02-09 7:17 ` george anzinger
-- strict thread matches above, loose matches on Subject: below --
2002-02-08 15:20 Tigran Aivazian
2002-02-08 15:36 ` Arjan van de Ven
2002-02-08 15:43 ` Rik van Riel
2002-02-08 15:52 ` Alan Cox
2002-02-08 20:08 ` Andrew Morton
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=20020208115755.E1429@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=tigran@veritas.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.