Evolution-x/hardware_interfaces
1
0
Fork 0
mirror of https://github.com/Evolution-X/hardware_interfaces synced 2026-02-01 16:09:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge "Clarify null-termination of name field" into main am: 8328cbb343 am: b47a11c1d5 am: 3f76bf5b23 am: 84816ec99d am: f5af8ff475 am: 2705f61931

Browse Source 
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2651037

Change-Id: I89154927eaf442ca05a3fcdf92fc1a1cc0e17139
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
Treehugger Robot
2023-07-07 22:47:09 +00:00
committed by Automerger Merge Worker
parent 467e7d4739 2705f61931
commit a68be420fd
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
graphics/allocator/aidl/android/hardware/graphics/allocator/BufferDescriptorInfo.aidl
View File

@@ -23,7 +23,14 @@ import android.hardware.graphics.common.PixelFormat;
@VintfStability
parcelable BufferDescriptorInfo {
/**
* The name of the buffer in ASCII. Useful for debugging/tracing.
* The name of the buffer in null-terminated ASCII. Useful for debugging/tracing.
*
* NOTE: While a well behaved client will ensure it passes a null-terminated string
* within the 128-byte limit, the IAllocator service implementation should be
* be defensive against malformed input. As such, it is recommended that
* IAllocator implementations proactively do `name[127] = 0` upon receiving
* an allocation request to enusre that the string is definitely
* null-terminated regardless of what the client sent.
*/
byte[128] name;