From: Andi Kleen <ak@muc.de>
To: "David S. Miller" <davem@redhat.com>
Cc: joern@wohnheim.fh-wedel.de, mingo@elte.hu, andrea@suse.de,
riel@redhat.com, torvalds@osdl.org, arjanv@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: 4k stacks in 2.6
Date: Wed, 26 May 2004 21:32:32 +0200 [thread overview]
Message-ID: <m38yff7zn3.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <20baw-1Lz-15@gated-at.bofh.it> (David S. Miller's message of "Wed, 26 May 2004 20:20:08 +0200")
"David S. Miller" <davem@redhat.com> writes:
>> Change gcc to catch stack overflows before the fact and disallow
>> module load unless modules have those checks as well.
It's impossible to do anything but panic, so it's not too helpful
in practice. You can only do better for interrupts
(not handle an interrupt when the stack is too low).
> That's easy, just enable profiling then implement a suitable
> _mcount that checks for stack overflow. I bet someone has done
> this already.
I did it for x86-64 a long time ago. Should be easy to port to i386
too.
ftp://ftp.x86-64.org/pub/linux/debug/stackcheck-1
-Andi
next prev parent reply other threads:[~2004-05-26 19:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ZQpn-1Rx-1@gated-at.bofh.it>
[not found] ` <1ZQz8-1Yh-15@gated-at.bofh.it>
[not found] ` <1ZRFf-2Vt-3@gated-at.bofh.it>
[not found] ` <203Zu-4aT-15@gated-at.bofh.it>
2004-05-26 13:57 ` 4k stacks in 2.6 Andi Kleen
2004-05-26 18:17 ` hch
2004-05-26 18:24 ` Andi Kleen
2004-05-26 20:39 ` Zwane Mwaikambo
[not found] ` <206b3-5WN-33@gated-at.bofh.it>
[not found] ` <20baw-1Lz-15@gated-at.bofh.it>
2004-05-26 19:32 ` Andi Kleen [this message]
2004-05-27 11:27 ` Jörn Engel
2004-05-27 13:49 ` Andrea Arcangeli
2004-05-27 14:15 ` Jörn Engel
2004-05-27 14:49 ` Andrea Arcangeli
2004-05-27 14:59 ` Jörn Engel
2004-05-27 15:08 ` Keith Owens
2004-05-27 15:21 ` Jörn Engel
2004-05-27 15:34 ` Arjan van de Ven
2004-05-27 15:46 ` Jörn Engel
2004-06-01 5:25 ` Jörn Engel
2004-05-26 15:17 Albert Cahalan
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 19:50 4g/4g for 2.6.6 Rik van Riel
2004-05-25 20:10 ` Rik van Riel
2004-05-25 21:15 ` Andrea Arcangeli
2004-05-26 10:33 ` 4k stacks in 2.6 Ingo Molnar
2004-05-26 12:50 ` Jörn Engel
2004-05-26 12:53 ` Arjan van de Ven
2004-05-26 13:00 ` Jörn Engel
2004-05-26 13:05 ` Arjan van de Ven
2004-05-26 16:41 ` Jörn Engel
2004-05-27 12:45 ` Ingo Molnar
2004-05-27 13:59 ` Andrea Arcangeli
2004-05-27 14:03 ` Arjan van de Ven
2004-05-27 14:42 ` Andrea Arcangeli
2004-06-02 19:40 ` Bill Davidsen
2004-05-27 14:18 ` Brian Gerst
2004-05-27 14:50 ` Andrea Arcangeli
2004-05-27 14:55 ` Linus Torvalds
2004-05-27 15:39 ` Andrea Arcangeli
2004-05-27 18:31 ` Guy Sotomayor
2004-05-27 19:26 ` Brian Gerst
2004-06-07 18:14 ` Timothy Miller
2004-06-08 6:26 ` Arjan van de Ven
2004-06-08 8:45 ` Jörn Engel
2004-05-26 18:12 ` David S. Miller
2004-05-26 19:02 ` Matt Mackall
2004-05-26 19:25 ` Dave Jones
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=m38yff7zn3.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=andrea@suse.de \
--cc=arjanv@redhat.com \
--cc=davem@redhat.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riel@redhat.com \
--cc=torvalds@osdl.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