From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] sigaltstack and RBS
Date: Sun, 09 Feb 2003 08:48:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805828@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805824@msgid-missing>
>>>>> On Sun, 9 Feb 2003 18:58:06 +1100, Matt Chapman <matthewc@cse.unsw.edu.au> said:
Matt> Here's a small test program.
Hmmh, the test program doesn't test backing-store _overflow_, it tests
what happens when you _remove_ a formerly valid mapping. The program
fails because the "rfi" that gets executed when returning from
mprotect() may end up trying to restore registers that got spilled to
the backing store before the call mprotect(), the mprotect() then
removes access permission and hence the "rfi" can never finish
execution (effectively, the mprotect() makes the contents of the
spilled stacked registers disappear for good).
The current sigaltstack implementation isn't designed to handle such a
case. And I'm not sure whether it should. Is there a particular
reason you want to do this sort of thing?
--david
next prev parent reply other threads:[~2003-02-09 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 5:19 [Linux-ia64] sigaltstack and RBS Matt Chapman
2003-02-09 5:27 ` David Mosberger
2003-02-09 5:47 ` Matt Chapman
2003-02-09 7:58 ` Matt Chapman
2003-02-09 8:48 ` David Mosberger [this message]
2003-02-09 10:55 ` Matt Chapman
2003-02-09 18:22 ` David Mosberger
2003-02-11 3:06 ` David Mosberger
2003-02-11 7:26 ` Matt Chapman
2003-02-11 19:11 ` David Mosberger
2003-03-07 23:35 ` Bjorn Helgaas
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=marc-linux-ia64-105590709805828@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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