Handle an invalid new frame request When HalCamera and VirtualCamera are synchronized based on the fences, it is possible that VirtualCamera sends a new frame request after a corresponding timeline/fence is destroyed. This change therefore add a logic to check the validity of the timeline associated with the requestor and, if it is not valid, returns an invalid fence to notify that a frame request is not queued. Fix: 169282240 Test: Run evs_halcamera_fuzzer and evs_virtualcamera_fuzzer Change-Id: I783454bcdca05f8f4d6b2b8eff118956d7155362 Merged-In: I783454bcdca05f8f4d6b2b8eff118956d7155362 (cherry picked from commit 0b188826a3f9584f2cfed02d3a73d834c8312a60) (cherry picked from commit a2163172e291093cba730f7113775442c8f8f244)
Native (C++) code format is required to be compatible with .clang-format file. Run
git clang-format --style=file --extension='h,cpp,cc' HEAD~
Note that clang-format is not desirable for Android java files. Therefore the command line above is limited to specific extensions.