From: Hugh Dickins <hugh@veritas.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Bill Irwin <bill.irwin@oracle.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wanted: simple, safe x86 stack overflow detection
Date: Tue, 6 Mar 2007 19:43:41 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703061937450.19813@blonde.wat.veritas.com> (raw)
In-Reply-To: <45EDBA1B.8050007@redhat.com>
On Tue, 6 Mar 2007, Chuck Ebbert wrote:
>
> In the 4k/4k stack i386 kernel, is there any fundamental reason it
> can't be 4k/8k? We seem to be mostly hitting problems in overflowing
> the IRQ stack... I think. Overhead would only be 4k per CPU for that.
For all of history prior to 2.6.20, there's been the fundamental
reason that even interrupt stacks need to access current_thread_info,
and that involved the (THREAD_SIZE - 1) mask. But 2.6.20's read_pda
using %gs gets away from that: my guess is that it's now possible
for i386 to use different sized stacks.
Hugh
next prev parent reply other threads:[~2007-03-06 19:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 14:27 Chuck Ebbert
2007-02-28 16:31 ` Thiago Galesi
2007-02-28 20:41 ` Andi Kleen
2007-02-28 23:20 ` Bill Irwin
2007-02-28 23:36 ` Jan Engelhardt
2007-02-28 23:45 ` Bill Irwin
2007-03-04 1:50 ` Bill Irwin
2007-03-06 18:59 ` Chuck Ebbert
2007-03-06 19:43 ` Hugh Dickins [this message]
2007-03-06 20:34 ` Bill Irwin
2007-03-07 4:28 ` Arjan van de Ven
2007-03-07 6:44 ` Bill Irwin
2007-03-07 12:34 ` Arjan van de Ven
2007-03-07 14:48 ` Bill Irwin
2007-03-07 15:04 ` Arjan van de Ven
2007-03-08 7:43 ` Avi Kivity
2007-03-19 20:53 ` Eric W. Biederman
2007-03-06 20:06 ` Bill Irwin
2007-03-05 1:18 ` Arnd Bergmann
2007-03-05 12:39 ` Andi Kleen
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=Pine.LNX.4.64.0703061937450.19813@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=andi@firstfloor.org \
--cc=bill.irwin@oracle.com \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®