android_packages_modules_Vi.../vm_payload
Alan Stokes e0945ad0e4 RPC Server never returns
In normal operation AVmPayload_runVsockRpcServer should never return -
the calling thread joins the server's thread pool, and we provide no
way to shut down the server. If the server does exit, that indicates a
failure somewhere.

If there is a failure of any sort (including unexepected server exit)
there is nothing the caller can do, so we panic rather than returning
a bool.

Update callers to not expect a return value.

I got slightly carried away and also:
- Modified compsvc to use AVmPayload_runVsockRpcServer rather than
  rolling its own.
- Turned on unsafe_op_in_unsafe_fn in the API implementation. That
  requires us to explicitly mark unsafe blocks in unsafe functions, so
  I've gone through and done that. I checked that all the top-level
  functions that should be marked unsafe are.

Bug: 243512108
Test: atest MicrodroidTests
Test: composd_cmd test-compile
Change-Id: I447ce0baa09d6a244ffe2ba7ab08092be3cd0f82
2022-11-25 10:14:14 +00:00
..
include RPC Server never returns 2022-11-25 10:14:14 +00:00
include-restricted Panic on non-actionable failures 2022-11-23 15:36:11 +00:00
src RPC Server never returns 2022-11-25 10:14:14 +00:00
Android.bp Run RpcBinder server for each VM on port==CID 2022-11-23 14:21:40 +00:00