Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit a68be420 authored by Treehugger Robot's avatar Treehugger Robot Committed by Automerger Merge Worker
Browse files

Merge "Clarify null-termination of name field" into main am: 8328cbb3 am:... 

Merge "Clarify null-termination of name field" into main am: 8328cbb3 am: b47a11c1 am: 3f76bf5b am: 84816ec9 am: f5af8ff4 am: 2705f619

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



Change-Id: I89154927eaf442ca05a3fcdf92fc1a1cc0e17139
Signed-off-by: default avatarAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
parents 467e7d47 2705f619

graphics/allocator/aidl/android/hardware/graphics/allocator/BufferDescriptorInfo.aidl

+8 −1
Original line number Diff line number Diff line
@@ -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;