From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: "Jan Beulich" <jbeulich@novell.com>,
"Eric Sandeen" <sandeen@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [discuss] [PATCH 1/2] (resend) x86_64 stack overflow debugging
Date: Wed, 14 Jun 2006 08:38:18 +0200 [thread overview]
Message-ID: <200606140838.18891.ak@suse.de> (raw)
In-Reply-To: <448FC7C0.76E4.0078.0@novell.com>
On Wednesday 14 June 2006 08:24, Jan Beulich wrote:
> Are you certain you will ever see this trigger? Assembly code switches to the special interrupt handling stack prior to calling do_IRQ(), so I can't see how you would ever find yourself on the process stack in stack_overflow_check(). Jan
The point of the code is to sample the original process stack
and check if the code there is a stack pig, not the interrupt.
I'm not sure it would be worth adding a special check for irqstack/exception
stacks because nesting there should be pretty rare. Probably not.
-Andi
prev parent reply other threads:[~2006-06-14 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 19:43 Eric Sandeen
2006-06-14 6:24 ` [discuss] " Jan Beulich
2006-06-14 6:38 ` Andi Kleen [this message]
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=200606140838.18891.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sgi.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 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®