Skip to content
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

RExec: Kill flow on unexpected messages #1

Closed
wants to merge 15 commits into from

Conversation

reynir
Copy link
Owner

@reynir reynir commented Oct 21, 2019

Kill the connection when another VM sends an unexpected message.

yomimono and others added 15 commits August 20, 2019 14:54
Co-authored-by: linse <sschirme@gmail.com>
Co-authored-by: linse <sschirme@gmail.com>
Co-authored-by: linse <sschirme@gmail.com>
Co-authored-by: Mindy <meetup@yomimono.org>
Co-authored-by: linse <sschirme@gmail.com>
Instead of as debug messages. We would not want to hide these.
Co-Authored-By: C For C's Sake <cfcs@users.noreply.github.com>
We raise an exception if the arguments do not fit in the cstruct.

Also some whitespace changes.
Try to reflect that it's the remote service exit code
@reynir
Copy link
Owner Author

reynir commented Oct 27, 2019

The server flow doesn't kill the connection on unexpected messages. We should probably do the same for both server and client.

What does the C implementation do?

@reynir
Copy link
Owner Author

reynir commented Sep 16, 2022

Merged in mirage#61

@reynir reynir closed this Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants