From: Chuck Ebbert <cebbert@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Tim Yamin <plasmaroo@gentoo.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH UPDATE] deflate stack usage in lib/inflate.c
Date: Thu, 12 Apr 2007 19:06:16 -0400 [thread overview]
Message-ID: <461EBB68.8010408@redhat.com> (raw)
In-Reply-To: <461EB938.6080807@goop.org>
Jeremy Fitzhardinge wrote:
> Andi Kleen wrote:
>>> (This was under Xen, but there's no reason it couldn't happen on bare
>>> hardware.)
>>>
>> Hmm, does Xen perhaps not use interrupt stacks?
>
> Looks like that's all done in do_IRQ, so it should be independent of
> whether its Xen or not. And the stack overflow check is performed on
> the main stack, before switching to the interrupt stack.
>
Yeah, the do_IRQ thing is misleading because it makes you think the
interrupt caused an overflow when all it did was detect a
near-overflow condition. (The number printed is the amount of space
left.)
next prev parent reply other threads:[~2007-04-12 23:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 8:25 [PATCH] deflate stack usage in lib/inflate.c Jeremy Fitzhardinge
2007-04-12 20:50 ` [PATCH UPDATE] " Jeremy Fitzhardinge
2007-04-12 21:21 ` Andi Kleen
2007-04-12 22:39 ` Jeremy Fitzhardinge
2007-04-12 23:20 ` Jan Engelhardt
2007-04-12 23:31 ` Jeremy Fitzhardinge
2007-04-12 23:37 ` Andi Kleen
2007-04-12 22:56 ` Jeremy Fitzhardinge
2007-04-12 23:02 ` Andi Kleen
2007-04-13 0:00 ` Jeremy Fitzhardinge
2007-04-12 23:06 ` Chuck Ebbert [this message]
2007-04-12 22:25 ` Matt Mackall
2007-04-12 22:57 ` Jeremy Fitzhardinge
2007-04-12 22:53 ` Matt Mackall
2007-04-16 21:04 ` Russell King
2007-04-13 18:42 ` Matt Mackall
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=461EBB68.8010408@redhat.com \
--to=cebbert@redhat.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plasmaroo@gentoo.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 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.