forked from envoyproxy/envoy
-
Notifications
You must be signed in to change notification settings - Fork 62
Add WASM SEGV handler and test. #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| NO_CONTEXT = true | ||
|
|
||
| all: logging.wasm bad_signature.wasm | ||
| all: logging.wasm bad_signature.wasm segv.wasm | ||
|
|
||
| include ../../../../api/wasm/cpp/Makefile.base |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| // NOLINT(namespace-envoy) | ||
| #include <string> | ||
|
|
||
| #include "proxy_wasm_intrinsics.h" | ||
|
|
||
| static int* badptr = nullptr; | ||
|
|
||
| extern "C" EMSCRIPTEN_KEEPALIVE void proxy_onStart() { | ||
| logError("before badptr"); | ||
| *badptr = 1; | ||
| logError("after badptr"); | ||
| } | ||
Binary file not shown.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to add
segv.wasmandsegv.watto this commit.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can I reproduce the failure you are seeing? When I run bazel test wasm_test in envoy/test/extensions/wasm I get:
//test/extensions/wasm:wasm_test PASSED in 2.4s
Which is to say I am seeing the Exception caught.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it works fine in mocked tests (since you're explicitly catching Exception using
EXPECT_THROW_WITH_MESSAGE), but that has nothing to do with "normal" usage.To reproduce that stacktrace, you can add
badptrcode to any WASM HTTP filter (e.g.headers.cc), recompile it, and start Envoy with it. Envoy should crash when executingbadptrcode.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, yes, from the unhandled Exception. I was thinking that generally we would convert all errors of this type to Exceptions so that we can catch them and signal the controller (istio) then unload/disable the filter but I haven't completed that code yet. I was expecting to do it in a later PR. I can capture the stack pointer/trace when I throw the Exception as well. That should generalize to this case as well as those covered by Runtime::catchRuntimeExceptions(). Do you have another design in mind. Let's talk offline.