From: Jes Sorensen <jes@sunsite.dk>
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: 08 Feb 2002 21:22:05 +0100 [thread overview]
Message-ID: <d3eljvlo5u.fsf@lxplus052.cern.ch> (raw)
In-Reply-To: <Pine.LNX.4.33.0202081645170.1359-100000@einstein.homenet>
In-Reply-To: Tigran Aivazian's message of "Fri, 8 Feb 2002 16:59:47 +0000 (GMT)"
Tigran Aivazian <tigran@veritas.com> writes:
> So, I found this patch useful at least for debugging. Moreover, I think it
> would be very useful to have it in Linus' kernel as a CONFIG_ option so
> that if people complain about random memory corruption then they can try
> to reproduce it with larger stack and then (with aid of /proc/stack) the
> offender is found and fixed. I cc'd Alan; if he thinks this is a bad idea
> I would be interested to know why.
Well as someone suggested, stick it under CONFIG_SLAB_DEBUG then, it
surely shouldn't be an option to be enabled in normal production
kernels but for debugging it's fine.
Jes
next prev parent reply other threads:[~2002-02-08 20:24 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
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 [this message]
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=d3eljvlo5u.fsf@lxplus052.cern.ch \
--to=jes@sunsite.dk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--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.