From: Jacques Gelinas <jack@solucorp.qc.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Whizzy New Feature: Paged segmented memory
Date: Tue, 8 Jan 2002 08:42:35 -0500 [thread overview]
Message-ID: <20020108084235.628e035081b2@remtk.solucorp.qc.ca> (raw)
On Tue, 8 Jan 2002 12:22:25 -0500, jtv wrote
> On Tue, Jan 08, 2002 at 02:17:14AM -0500, Anthony DeRobertis wrote:
> >
> > A nice thing about two stacks is that it can be a completely
> > userspace thing. No need to involve the kernel at all; just gcc
> > and friends.
>
> Doesn't it have ABI implications as well?
Yes, it might make the whole thing binary incompatible (so we could
have a new glibc major release :-) ) Not sure.
> If so, why not go all the way and have stacks grow upwards? :-)
This won't help. It will change the attack pattern though (so it may help
a bit). If the stack grow upward, then the data from the caller, passed to the
callee will be used to create the overflow. Taking control this way is still
possible.
And the stack grow direction is controlled by the CPU stack operation and
we can't change it.
---------------------------------------------------------
Jacques Gelinas <jack@solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!
http://www.solucorp.qc.ca/miscprj/s_context.hc
next reply other threads:[~2002-01-08 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 13:42 Jacques Gelinas [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-08 3:45 Jacques Gelinas
2002-01-08 7:17 ` Anthony DeRobertis
2002-01-08 11:22 ` jtv
2002-01-08 14:05 ` Anthony DeRobertis
2002-01-08 14:14 ` Richard B. Johnson
2002-01-08 19:33 ` Anthony DeRobertis
2002-01-08 19:45 ` Richard B. Johnson
2002-01-08 17:11 ` jtv
2002-01-08 19:32 ` Anthony DeRobertis
2002-01-06 14:14 Marcin Tustin
2002-01-06 18:32 ` Gábor Lénárt
2002-01-06 20:41 ` Kevin Krieser
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=20020108084235.628e035081b2@remtk.solucorp.qc.ca \
--to=jack@solucorp.qc.ca \
--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®