diff options
author | Paul Elder <paul.elder@ideasonboard.com> | 2021-07-20 19:24:47 +0900 |
---|---|---|
committer | Paul Elder <paul.elder@ideasonboard.com> | 2021-08-19 16:54:02 +0900 |
commit | 31078711d6c3639073db97322c6f7d98dacbbefe (patch) | |
tree | cf684773f11124218cbdfb07337a24a92eb48fb9 /src/android/data/nautilus/camera_hal.yaml | |
parent | e35cae067980a62b23d25792bc5176b4c554605f (diff) |
ipa: Use FileDescriptor instead of int in layers above IPC payload
Regarding (de)serialization in isolated IPA calls, we have four layers:
- struct
- byte vector + fd vector
- IPCMessage
- IPC payload
The proxy handles the upper three layers (with help from the
IPADataSerializer), and passes an IPCMessage to the IPC mechanism
(implemented as an IPCPipe), which sends an IPC payload to its worker
counterpart.
When a FileDescriptor is involved, previously it was only a
FileDescriptor in the first layer; in the lower three it was an int. To
reduce the risk of potential fd leaks in the future, keep the
FileDescriptor as-is throughout the upper three layers. Only the IPC
mechanism will deal with ints, if it so wishes, when it does the actual
IPC. IPCPipeUnixSocket does deal with ints for sending fds, so the
conversion between IPCMessage and IPCUnixSocket::Payload converts
between FileDescriptor and int.
Additionally, change the data portion of the serialized form of
FileDescriptor to a 32-bit unsigned integer, for alightnment purposes
and in preparation for conversion to an index into the fd array.
Also update the deserializer of FrameBuffer::Plane accordingly.
Signed-off-by: Paul Elder <paul.elder@ideasonboard.com>
Tested-by: Umang Jain <umang.jain@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Umang Jain <umang.jain@ideasonboard.com>
Diffstat (limited to 'src/android/data/nautilus/camera_hal.yaml')
0 files changed, 0 insertions, 0 deletions