diff options
| author | Peter Collingbourne <peter@pcc.me.uk> | 2016-05-24 23:38:02 +0000 |
|---|---|---|
| committer | Peter Collingbourne <peter@pcc.me.uk> | 2016-05-24 23:38:02 +0000 |
| commit | e8a97b24a38889b92879ddb3bd313dfd3b1519d5 (patch) | |
| tree | 73deed2e85ca7e7ea7c7cd54849b49fae10abc91 /docs/SafeStack.rst | |
| parent | f042fe468be9254e12ec528d73c93f252ff331b3 (diff) | |
docs: Document how safestack handles setjmp and exceptions.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@270634 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/SafeStack.rst')
| -rw-r--r-- | docs/SafeStack.rst | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/SafeStack.rst b/docs/SafeStack.rst index 21e9b6c621..f01b75f5cb 100644 --- a/docs/SafeStack.rst +++ b/docs/SafeStack.rst @@ -178,6 +178,17 @@ Please refer to the `Code-Pointer Integrity <http://dslab.epfl.ch/proj/cpi/>`__ project page for more information about the design of the SafeStack and its related technologies. +setjmp and exception handling +----------------------------- + +The `OSDI'14 paper <http://dslab.epfl.ch/pubs/cpi.pdf>`_ mentions that +on Linux the instrumentation pass finds calls to setjmp or functions that +may throw an exception, and inserts required instrumentation at their call +sites. Specifically, the instrumentation pass saves the shadow stack pointer +on the safe stack before the call site, and restores it either after the +call to setjmp or after an exception has been caught. This is implemented +in the function ``SafeStack::createStackRestorePoints``. + Publications ------------ |